Disk Graphs
list Vernon Everett
Hi Henrik/all I just noticed something interesting with disk graphs. Last night, one of my disks hit 99% (for a few minutes) which made me look more closely at the history graph _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ NOTICE: This message and any attachments are confidential and may contain copyright material of Australian Finance Group Limited or a third party. It is intended solely for the purpose of the addressee and any other named recipient. If you are not the intended recipient, any use, distribution, disclosure or copying of this message is strictly prohibited. The confidentiality attached to this message is not waived or lost by reason of the mistaken transmission or delivery to any unintended party. If you have received this message in error, please notify the author immediately or contact Australian Finance Group on +61 8 9420 7888.
list Vernon Everett
Dunno what happened there, but it wasn't supposed to send just yet.
Let's try again.
Hi Henrik/all
I just noticed something interesting with disk graphs.
Last night, one of my disks hit 99% (for a few minutes) which made me look more closely at the history graphs for the disk in question.
The 48 hour graph shows Max to be 99% - No worries there.
The 12 day graph shows it to be 95.5%
The 48 day only 65.3, and the 576 day, a tiny 39.9%
However, every night, since I started monitoring, this disk hits over 95% for a few minutes. (An overnight process uses the space then releases it)
Have I found a bug with Hobbit/RRDTool, or am I doing something silly?
Regards
Vernon
P.S. Running Hobbit 4.0.3 with rrdtool 1.0.49
▸
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
NOTICE: This message and any attachments are confidential and may contain copyright material of Australian Finance Group Limited or a third party. It is intended solely for the purpose of the addressee and any other named recipient. If you are not the intended recipient, any use, distribution, disclosure or copying of this message is strictly prohibited. The confidentiality attached
to this message is not waived or lost by reason of the mistaken transmission or delivery to any unintended party. If you have received this message in error, please notify the author immediately or contact Australian Finance Group on +61 8 9420 7888.
list Henrik Størner
▸
On Tue, May 31, 2005 at 08:31:16AM +0800, Vernon Everett wrote:
I just noticed something interesting with disk graphs. Last night, one of my disks hit 99% (for a few minutes) which made me look more closely at the history graphs for the disk in question. The 48 hour graph shows Max to be 99% - No worries there. The 12 day graph shows it to be 95.5% The 48 day only 65.3, and the 576 day, a tiny 39.9% However, every night, since I started monitoring, this disk hits over 95% for a few minutes. (An overnight process uses the space then releases it) Have I found a bug with Hobbit/RRDTool, or am I doing something silly?
It's not a bug, but it's a common misunderstanding about how RRDtool handles data for the graphs. The min/max values you see on the graphs are not absolute min/max values. RRDtool doesn't keep any record of these. What RRDtool does is to compute an average value for each data point, an average over the amount of time each data point represents in the graph. And the min/max values you get are the lowest/highest value of that *average*. Each graph has 576 data points. For the 48-hour graph this means a data point is the average over 5 minutes - which happens to match the frequency that most of the Hobbit tests run. So the 48-hour graph more or less matches the absolute measurements done (not quite, because the tests can run at intervals that are not exactly 5 minutes). The 12 day graph averages over 30 minutes, the 48 day graph over 2 hours, and the 576 day graph over 24 hours. So if your disk is 35% full all of the time, except for 5 minutes a day, then the 576-day graph will come out as being completely flat - because the average value *over the 24-hour period* will be constant. And you'll see a max-value of (5*95 + 1435*35)/1440 = 35,2 % (24 hours = 1440 minutes). Regards, Henrik
list Thomas Kaehn
Hi,
is client based configuration fully supported or is it considered
deprecated? Are there some features which do not work using client
based configuration (e.g. logfile monitoring or viewing client data
in the web interface)?
I've noticed that the disk graphs do not show all filesystems reported
by the clients. There is always one filesystem missing (count in the
script URL one too low). However on the trends page the graph shows up
correctly. Is it a bug or configuration issue?
Ciao,
Thomas
--
Thomas Kähn WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Im Süsterfeld 6 Tel 0241/701333-18
user-02a72cb3f725@xymon.invalid D-52072 Aachen Fax 0241/911879
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Die Gesellschaft ist eingetragen im Handelsregister Aachen unter HRB 7608
Geschäftsführer: Thomas Neugebauer, Thomas Heller, Michael Kolb
list Thomas Kaehn
Hi,
▸
On Mon, Oct 15, 2007 at 12:09:00PM +0200, Thomas Kaehn wrote:I've noticed that the disk graphs do not show all filesystems reported by the clients. There is always one filesystem missing (count in the script URL one too low). However on the trends page the graph shows up correctly. Is it a bug or configuration issue?
I've taken a closer look at this problem. It does not occur with any number of filesystems. 5 filesystems => only 4 are shown in 1 diagram 6 filesystems => only 5 are shown in 1 diagram 1 filesystem => OK, 1 diagram 10 filesystems => OK, 3 diagrams 14 filesystems => OK, 4 diagrams Additionally the wrong number of graphs is only shown on the disk page not on the trends page. Is anyone experiencing the same problem?
▸
is client based configuration fully supported or is it considered deprecated? Are there some features which do not work using client based configuration (e.g. logfile monitoring or viewing client data in the web interface)?
Ciao,
Thomas
--
Thomas Kähn WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Im Süsterfeld 6 Tel 0241/701333-18
user-02a72cb3f725@xymon.invalid D-52072 Aachen Fax 0241/911879
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Die Gesellschaft ist eingetragen im Handelsregister Aachen unter HRB 7608
Geschäftsführer: Thomas Neugebauer, Thomas Heller, Michael Kolb
list Tom Schmitt
I would like to front end the ack of an outage by having the person call
into an Asterisk PBX-in-a-Flash(PiaF) system.
The user would then be prompted for the associate information.
The script would then ssh (no-password/using cert) to the Xymon system
and issue a command line to ack the outage.
Is there a place you can point me to the ack info using the command
line.
I do not currently have any ack functions working other than the web
page.
I have already created scripts that use the .call file functions to send
a Text-to-Speech (TTS) message if there are specific problems.
I think that the marriage of the two systems can be a very good way to
do out-of-band notification is the Internet or Email are having a
problem.
Thanks,
Tom Schmitt
Senior IT Staff - R&D
L-3 Communication Systems West
640 North 2200 West
P.O. Box 16850
Salt Lake City, UT XXXXX
Phone (XXX) XXX-XXXX
Cell (XXX) XXX-XXXX
eFax (XXX) XXX-XXXX
user-9c1ae820b621@xymon.invalid
\\\\||////
\ ~ ~ /
| @ @ |
--oOo---(_)---oOo--
list Ricardas Vaitkus
Hi all. I have faced proble, described by Thomas Kaehn (2007 October). But still I am unable to find solution Some times, some of disk graphs are not displayed, but in trend graphs it is shown. Has anyone found solution for that known issue? Thanks. Ricardas
list Buchan Milne
▸
----- "d tom schmitt" <user-9c1ae820b621@xymon.invalid> wrote:
I would like to front end the ack of an outage by having the person call into an Asterisk PBX-in-a-Flash(PiaF) system. The user would then be prompted for the associate information. The script would then ssh (no-password/using cert) to the Xymon system and issue a command line to ack the outage. Is there a place you can point me to the ack info using the command line.
Line 110 of web/hobbit-ackinfo.c has the following:
/* ackinfo HOST.TEST\nlevel\nvaliduntil\nackedby\nmsg */
bbmsg = (char *)malloc(1024 + strlen(hostname) + strlen(testname) + strlen(ackedby) + strlen(ackmsg));
sprintf(bbmsg, "ackinfo %s.%s\n%d\n%d\n%s\n%s\n",
hostname, testname, level, validity, ackedby, ackmsg);
res = sendmessage(bbmsg, NULL, NULL, NULL, 0, BBTALK_TIMEOUT);
So, it would appear you should be able to use 'bb' to send an appropriate message, as shown in the comment.
(this could be added to the 'bb' man page if it would be of interest).
Regards,
Buchan