DISK IGNORE useage 🔗 link

On 01/24/2011 11:01 AM, Rob Munsch wrote:

I think I’m missing something.  I have

 
Filesystem         1024-blocks      Used Available Capacity Mounted on

/dev/hdv1            3768053780 1056651192 2711402588      29% /

none                    131072       336    130736       1% /tmp

 
and they’re both graphed.  Except the /dev/hdv1 is the entire array and
I don’t want to monitor that – just /tmp.  (In our last episode, I got
it to monitor /tmp by grep –v-ing for tempfs in the client’s DF line).

 
However… if I add to the host’s config a DISK IGNORE /, then while the
text (as above) only shows /tmp, I lose /tmp’s graph line and it only
graphs root.  I’ve tried including the IGNORE line both before and after
a line for /tmp, with no effect.  As soon as I add the IGNORE line,
/tmp’s graph line vanishes on next update. 

On 01/24/2011 02:06 PM, Clark, Sean wrote:

I just compiled and installed RC1 on a Red Hat EL5.5 server this AM, and have come across a strange issue – don't know if it's my configuration or something with the new version

It seems like it isn't following the DURATION flag for alerts

I have some rules for a host, it matches on two lines:


./xymond_alert --test hostname.subdomain.domain.com disk
00003158 2011-01-24 13:51:05 send_alert hostname.subdomain.domain.com:disk state Paging
00003158 2011-01-24 13:51:05 Matching host:service:page 'hostname.subdomain.domain.com:disk:unified-tex' against rule line 128
00003158 2011-01-24 13:51:05 *** Match with 'HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh' ***
00003158 2011-01-24 13:51:05 Matching host:service:page 'hostname.subdomain.domain.com:disk:unified-tex' against rule line 134
00003158 2011-01-24 13:51:05 *** Match with 'HOST=% SERVICE=%disk|inode|procs|temperature' ***


here is the alerts.cfg relevent sections:


   128  HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh
   129   MAIL=user-ac2e53899896@xymon.invalid DURATION>20 REPEAT=60 COLOR=red RECOVERED


   134  HOST=% SERVICE=%disk|inode|procs|temperature
   135   MAIL=user-c96a031d3d93@xymon.invalid TIME=06:0000:2359 DURATION>720 REPEAT=120 COLOR=red RECOVERED
   136   MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:0000:0559 DURATION>720 REPEAT=120 COLOR=red RECOVERED
   137   MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:0600:1759 DURATION>60 REPEAT=120 COLOR=red RECOVERED
   138   MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:1800:2359 DURATION>720 REPEAT=120 COLOR=red RECOVERED


What i am expecting from these rules/matches is

email mailing-list  if it's been red for > 20 minutes, and email on recovery

additionally

on Sat, Sunday, if it's been red for > 720 minutes, email my phone
on M-F, email my phone if it's been red for > 720 minutes & before 6am
after 7am, red > 60 minutes, after 6pm > 7200 minutes again


What is happening is

When a red even occurs, it immediately sends an email to user-ac2e53899896@xymon.invalid , and an email to user-c96a031d3d93@xymon.invalid


Does anyone know if this is my configuration that needs fixing , or something with 4.3.0?


-Sean


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

- -- - ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

On 1/24/11 2:32 PM, "Ryan Novosielski" <user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Please do not thread hijack (that is to say, reply to a message, change
its contents and subject and send that as a new message). These messages
still contain an In-Reply-To: header that irritates people with a
threaded mail reader. Please compose new messages instead.

I'd post a link on ettiquette but apparently someone has erased the
Wikipedia definition.

On 01/24/2011 02:06 PM, Clark, Sean wrote:
I just compiled and installed RC1 on a Red Hat EL5.5 server this AM, and have come across a strange issue – don't know if it's my configuration or something with the new version
It seems like it isn't following the DURATION flag for alerts
I have some rules for a host, it matches on two lines:
./xymond_alert --test hostname.subdomain.domain.com disk
00003158 2011-01-24 13:51:05 send_alert hostname.subdomain.domain.com:disk state Paging
00003158 2011-01-24 13:51:05 Matching host:service:page 'hostname.subdomain.domain.com:disk:unified-tex' against rule line 128
00003158 2011-01-24 13:51:05 *** Match with 'HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh' ***
00003158 2011-01-24 13:51:05 Matching host:service:page 'hostname.subdomain.domain.com:disk:unified-tex' against rule line 134
00003158 2011-01-24 13:51:05 *** Match with 'HOST=% SERVICE=%disk|inode|procs|temperature' ***
here is the alerts.cfg relevent sections:
    128  HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh

What i am expecting from these rules/matches is
email mailing-list  if it's been red for > 20 minutes, and email on recovery
additionally
on Sat, Sunday, if it's been red for > 720 minutes, email my phone
on M-F, email my phone if it's been red for > 720 minutes & before 6am
after 7am, red > 60 minutes, after 6pm > 7200 minutes again
What is happening is

Does anyone know if this is my configuration that needs fixing , or something with 4.3.0?
-Sean
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0908kACgkQmb+gadEcsb6UvQCeLD6q9TmVwlTyiy7hSvoFR73b
G3cAoKVghoHR1qbCVlsUsd5Lc2MtysQV
=j//M
-----END PGP SIGNATURE-----

On Mon, 24 Jan 2011 11:01:25 -0500, Rob Munsch wrote:

I think I’m missing something.  I have
 
Filesystem         1024-blocks      Used Available Capacity Mounted on
/dev/hdv1            3768053780 1056651192 2711402588      29% / 
none                     131072        336     130736       1% /tmp

and they’re both graphed.  Except the /dev/hdv1 is the entire array and
I don’t want to monitor that – just /tmp.  (In our last episode, I got
it to monitor /tmp by grep –v-ing for tempfs in the client’s DF line).
 
However… if I add to the host’s config a DISK IGNORE /, then while the
text (as above) only shows /tmp, I lose /tmp’s graph line and it only
graphs root.  I’ve tried including the IGNORE line both before and after
a line for /tmp, with no effect.  As soon as I add the IGNORE line,
/tmp’s graph line vanishes on next update.

In <user-e017fc110f76@xymon.invalid> Larry Barber <user-6ef9c2864140@xymon.invalid> writes:

Is there any way to configure the new menu bar so that it has a hierarchical
structure. In my current Hobbit installation I have the menus set up so that
I can navigate directly to any of the static pages in any of my pagesets by
navigating down a menu. Is there some way to duplicate this with the new
menu system?

On Mon, 24 Jan 2011 14:06:14 -0500, Clark, Sean wrote:

It seems like it isn't following the DURATION flag for alerts

I have some rules for a host, it matches on two lines:


./xymond_alert --test hostname.subdomain.domain.com disk 00003158
2011-01-24 13:51:05 send_alert hostname.subdomain.domain.com:disk state
Paging 00003158 2011-01-24 13:51:05 Matching host:service:page
'hostname.subdomain.domain.com:disk:unified-tex' against rule line 128
00003158 2011-01-24 13:51:05 *** Match with 'HOST=%

Clark, Sean <mailto:user-2db5fbcae9a7@xymon.invalid> wrote:

I just compiled and installed RC1 on a Red Hat EL5.5 server
this AM, and have come across a strange issue - don't know if
it's my configuration or something with the new version

It seems like it isn't following the DURATION flag for alerts

 
<snip>

here is the alerts.cfg relevent sections:


   128  HOST=% SERVICE=%disk|inode|procs|temperature|bbd|http|conn|ssh
   129   MAIL=user-ac2e53899896@xymon.invalid DURATION>20 REPEAT=60
COLOR=red RECOVERED


   134  HOST=% SERVICE=%disk|inode|procs|temperature
   135   MAIL=user-c96a031d3d93@xymon.invalid TIME=06:0000:2359
DURATION>720 REPEAT=120 COLOR=red RECOVERED
   136   MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:0000:0559
DURATION>720 REPEAT=120 COLOR=red RECOVERED
   137   MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:0600:1759
DURATION>60 REPEAT=120 COLOR=red RECOVERED
   138   MAIL=user-c96a031d3d93@xymon.invalid TIME=12345:1800:2359
DURATION>720 REPEAT=120 COLOR=red RECOVERED


What i am expecting from these rules/matches is

email mailing-list  if it's been red for > 20 minutes, and
email on recovery

<snip> 

What is happening is

When a red even occurs, it immediately sends an email to
user-ac2e53899896@xymon.invalid , and an email to user-c96a031d3d93@xymon.invalid


Does anyone know if this is my configuration that needs
fixing , or something with 4.3.0?


-Sean

Larry Barber <user-6ef9c2864140@xymon.invalid> writes:

Is there any way to configure the new menu bar so that it has a
hierarchical
structure. In my current Hobbit installation I have the menus set up so
that
I can navigate directly to any of the static pages in any of my pagesets
by
navigating down a menu. Is there some way to duplicate this with the new
menu system?

Probably, since it is "just" CSS. However, you'll have to find someone
with more CSS knowledge than me to tell you how to do it.


Regards,
Henrik

However… if I add to the host’s config a DISK IGNORE /, then while the
text (as above) only shows /tmp, I lose /tmp’s graph line and it only
graphs root.  I’ve tried including the IGNORE line both before and after
a line for /tmp, with no effect.  As soon as I add the IGNORE line,
/tmp’s graph line vanishes on next update.

Try this:

HOST=foo
	DISK %^/$ IGNORE

so you use a regex pattern that only matches "/" to ignore that
filesystem.

On Tue, 25 Jan 2011 09:49:03 -0500, Rob Munsch wrote:

However… if I add to the host’s config a DISK IGNORE /, then while
the text (as above) only shows /tmp, I lose /tmp’s graph line and it
only graphs root.  I’ve tried including the IGNORE line both before
and after a line for /tmp, with no effect.  As soon as I add the
IGNORE line, /tmp’s graph line vanishes on next update.

Try this:

HOST=foo
	DISK %^/$ IGNORE

so you use a regex pattern that only matches "/" to ignore that
filesystem.

I was expecting this to work - but now I have

Filesystem         1024-blocks      Used Available Capacity Mounted on
none                    131072     15456    115616      12% /tmp

and below it, / is graphed.  The graph line for /tmp vanished.  I'm very
confused.

In <!&!AAAAAAAAAAAuAAAAAAAAAL60wriLM9cRsTVojW0AAAABAFEdQVQs6tMRsLEAoMxarIMAAAABk2cAABAAAACnWr0Vk4vBSZ46JyBPrkK2AQAAAAA=@syntec.co.uk> "SebA" <user-7b2156f36779@xymon.invalid> writes:

One question I have if Henrik is reading this is, can I use custom colours,
e.g. orange, and put that in ALERTCOLORS instead of yellow?  

-----Original Message-----
From: Henrik Størner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Tuesday, January 25, 2011 10:22 AM
To: xymon at xymon.com
Subject: Re: [xymon] DISK IGNORE useage

On Tue, 25 Jan 2011 09:49:03 -0500, Rob Munsch wrote:

However… if I add to the host’s config a DISK IGNORE /, then while
the text (as above) only shows /tmp, I lose /tmp’s graph line and it
only graphs root.  I’ve tried including the IGNORE line both before
and after a line for /tmp, with no effect.  As soon as I add the
IGNORE line, /tmp’s graph line vanishes on next update.

Try this:

HOST=foo
	DISK %^/$ IGNORE

so you use a regex pattern that only matches "/" to ignore that
filesystem.

I was expecting this to work - but now I have

Filesystem         1024-blocks      Used Available Capacity Mounted on
none                    131072     15456    115616      12% /tmp

and below it, / is graphed.  The graph line for /tmp vanished.  I'm very
confused.

Hmm, yes - that can happen because you now have two RRD graph files, but
only one graph showing up on the webpage. You should have both of them
on the graph in the "trends" column, though.

Either wait 48 hours - then the root-filesystem graph will go "stale" and
automatically be ignored on the "disk" status graph display. Or you can go
to the ~hobbit/data/rrd/HOSTNAME/ directory and delete/rename the
"disk,root.rrd" file out of the way.