[Xymon] how to enable/disable an alert automatically (or make an alert conditional upon something else)?

[Root, Paul T]

I have secondary/proxy servers that monitor the primary. If it can’t get to (ping) the primary, it takes over.  The script, moves the alerts.cfg file in place that will actually do the alerts. Normally, the secondary’s alerts.cfg only has the test for the primary server.



From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Ribeiro, Glauber
Sent: Monday, August 28, 2017 2:46 PM
To: xymon at xymon.com
Subject: [Xymon] how to enable/disable an alert automatically (or make an alert conditional upon something else)?

Hello,

We have a very common situation where there are 2 servers, one being the production server, and the other its “spare”. If anything happens to the production server, we need people to be alerted even if it’s the middle of the night. On the other hand, if the spare server has problems, we may not need to wake people up.

The server roles swap periodically (the one that is production this month may be spare next month, and vice versa).

I can tell which one is production by watching for the existence of certain “flag files”, but I can imagine other places would have different mechanisms.

The question is: is there a way in xymon, to make an alert conditional on some other piece of information? Some way to handle this kind of situation, where the “decision” on the criticality of a server is outside xymon?

I think I could handle this by sending the alert to a script, and having logic in the script to send the communication or not. But I’m wondering if there is a better way, and I imagine that this kind of situation is common enough that people here must have seen it.

Thanks,

glauber
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20170828/ff0ae32d/attachment.html>