[Xymon] routing between xymons

[Ron Cohen]

Thanks for the suggestions guys, however:

The monitoring team use the non-green page for the monitoring. This page
includes all alerts, whether propagated or not. Also, I can't hide the
non-production alerts, since those should be acted upon by other support
teams, which will also use the non-green as their main monitor.

I'm not using the Critical view, since the alerts scripts (and the
analysis.conf, using the TEXT property) generate URLs to specific expert
advice for the monitoring team, so they can assign an incident to the
appropriate groups. Also, as per the above, what's required is separating
the alerts.


many thanks
_rony


On 13 May 2016 at 16:56, John Thurston <john.thurston at alaska.gov> wrote:

> On 5/13/2016 7:13 AM, Ron Cohen wrote:
>
>> Hello there...
>> we have here a pretty big production environments, and even bigger
>> non-production.
>> I've configured xymon for both, but the guys that do the actual
>> monitoring objected to have alerts coming from non-production servers,
>> since those are mostly non-crucial - they don't want to see any of those
>> reds on their screens.
>>
>
> One way that comes to mind is using the "nopropyellow" (etc) tags on the
> hosts. We mix our production and test hosts on pages, but mark the test
> hosts not to propagate their alerts upward. Their test results appear on
> their own page, but not on their parent page. Also look into the
> "nonongreen" tag.
>
> Note: the tags mentioned above affect the generation and display of the
> web pages. They do no affect alerts or the behavior of xymondboard.
>
> --
>    Do things because you should, not just because you can.
>
> John Thurston    907-465-8591
> John.Thurston at alaska.gov
> Enterprise Technology Services
> Department of Administration
> State of Alaska
>
> _______________________________________________
> 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/20160516/539959c0/attachment.html>