[Xymon] Alert issue
cleaver at terabithia.org
Thu Nov 12 20:56:02 CET 2015
On 11/12/2015 9:37 AM, David Welker wrote:
> Using your idea...
> PAGE=mypage COLOR=red,yellow
> MAIL me at here.com <mailto:me at here.com>
> ...when cpu is green, yellow, purple, or red --test now always returns
> a mail -s with CRITICAL (RED) message.
> which may actually BE correct, since elsewhere on the page there is a
> red status and I've now put the COLOR on the main line referencing the
> whole page. In an attempt to narrow it back down to the one host,
> however, I used HOST=^Server1*, instead of PAGE=, but STILL get the
> CRITICAL (RED) message in the --test run, but actually got an email
> regarding the yellow cpu status (and not for a different yellow status
> on the same page).
> --dump-config returns...
> HOST=^Server1* COLOR=yellow,red <---- NOTICE REVERSED COLORS (see
> MAIL me at here.com <mailto:me at here.com> FORMAT=TEXT REPEAT=30
> Interestingly enough, when I use a --color parameter with the --test,
> it performs correctly...
> If --color of cpu is yellow, --test returns a warning (YELLOW) message.
> If --color of cpu is red, --test returns a CRITICAL (RED) message.
> If --color of cpu is green or purple, --test returns a FAILED (due to
> color) message.
> By the way, my ALERTCOLORS="red,yellow,purple"
> Could it possibly be that the --test feature needs more testing, and
> that the alerting is actually working the way I expect it should?
Actually, this could be more of a documentation issue I suppose.
xymond_alert when in --test mode should really always have a --color=
specified (so that it knows what to test for).
Based on how it responded after you'd added that in, I believe it's
working as intended there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Xymon