[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] [re-post] xymon notifications
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] [re-post] xymon notifications
- From: J Sloan <joe (at) tmsusa.com>
- Date: Wed, 27 May 2009 13:06:18 -0700
- References: <4A1D8E86.5060506 (at) tmsusa.com> <997a524e0905271230g7091cab5v7416f35a85c7d34f (at) mail.gmail.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090318 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666
Ralph Mitchell wrote:
> On Wed, May 27, 2009 at 2:03 PM, J Sloan <joe (at) tmsusa.com
> <mailto:joe (at) tmsusa.com>> wrote:
>
> We've been running big brother for some years, and we monitor several
> hundred servers in 2 data centers.
>
> We are currently running a pilot of xymon (4.3.0 svn), and just as
> with
> big brother, we have redundant monitoring servers. A xymon server in
> california monitors hosts in both california and arizona, and a xymon
> server in arizona monitors hosts in both data centers as well.
>
> For the most part, xymon is performing well, but it is a bit of an
> annoyance with xymon that we get duplicate notifications, as each
> xymon
> server sends it's own notifications for every event.
>
> Big brother sends a single notification for each event, as
> controlled by
> the alerting failover.
>
> Is there any way to suppress the duplicate notifications from xymon?
>
>
> I don't think xymon has failover yet. How are you sending the
> alerts?? If you're using a script, you could make the script on the
> backup server run a check against the primary. If it fails, allow the
> backup to send out the notifications. Not perfect, but it could at
> least reduce the duplicates.
We're using the mail facility - for instance:
$LXADM=MAIL joe TIME=W:0800:1800 REPEAT=30m
$LXDNS=%(emerald|ebony|mulholland|plifsp01|plifsp10).*
HOST=$LXDNS
$LXADM RECOVERED
Joe