[Xymon] system reboot email alert

[Robert Herron]

Check out the UP parameter/setting in the analysis.cfg.  (
https://www.xymon.com/help/manpages/man5/analysis.cfg.5.html):

*UP bootlimit toolonglimit [color]*

The cpu status goes yellow/red if the system has been up for less than
"bootlimit" time, or longer than "toolonglimit". The time is in minutes, or
you can add h/d/w for hours/days/weeks - eg. "2h" for two hours, or "4w"
for 4 weeks.

Defaults: bootlimit=1h, toolonglimit=-1 (infinite), color=yellow.


So, you could add "UP 30m -1 RED" to either the DEFAULT stanza or to select
hosts.  The CPU test will then have a "&red Machine recently rebooted"  at
the top (similar to this
<https://www.xymon.com/xymon-cgi/historylog.sh?HOST=brahms.hswn.dk&SERVICE=cpu&TIMEBUF=Mon_Jul_7_22:59:08_2014>)
when the host's uptime <= 30m.


Robert Herron
robert.herron at gmail.com


On Thu, Jul 10, 2014 at 11:24 AM, Bauer-Lee, Sue <
Sue.Bauer-Lee at multiplan.com> wrote:

>  Hello All!
>
>
>
> Times have changed a bit in the infrastructure environment such that many
> have a large contingent of virtual machines and blades. These hosts tend to
> reboot rather quickly, hence connectivity failures tend to not get noticed.
> I have a request on the table to send an email alert with a specific
> subject line to indicate that a host has rebooted.
>
>
>
> I’ve seen a few posts over the years regarding requests to alert for
> system reboots. I also saw a post or two about adding a dynamic column
> capability. Some responses suggested an external script to accomplish the
> task of emailing an alert.
>
>
>
> I’m asking the question again because as I peruse the analysis.cfg and
> review the rules, I know I can issue an email alert for PROC and DISK.
>
> That begs the question of ‘why can’t I issue an email alert for UP’? I’m
> fine with the ‘yellow’ on CPU test for recent reboot, but since it also
> includes load changes, I’m not interested in a generic email for either one
> when they occur.
>
>
>
> If I already can, how??
>
>
>
> And if not, suggestions for a simple approach? I’m not exactly getting the
> desired results server-wide with an external script that should just send
> an email for a CPU status color=yellow without interfering with our other
> configured alerts. L
>
>
>
> Is someone already successfully conquering this task?
>
>
>
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> *NOTICE OF CONFIDENTIALITY: This message and any attachments contains
> confidential information belonging to the sender intended only for the use
> of the individual or entity named above. If you are not the intended
> recipient, be advised that copying, disclosure or reliance upon the
> contents is strictly prohibited. If you have received this message in error
> please notify the sender immediately.  *
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20140712/f18716af/attachment.html>