[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xymon] Monitoring Exchange 2010 - imaps/pop3s alarms
- To: xymon (at) xymon.com
- Subject: Re: [xymon] Monitoring Exchange 2010 - imaps/pop3s alarms
- From: epperson (at) alumni.unc.edu
- Date: Fri, 19 Nov 2010 12:16:26 -0500
- Importance: Normal
- References: <4CE5944C.60307 (at) elyograg.org> <5099428b5e9587aab5e0c387b46a4451.squirrel (at) epperson.homelinux.net> <4CE697CB.9040301 (at) elyograg.org>
- User-agent: SquirrelMail/1.4.21-1.fc12
On Fri, November 19, 2010 10:29, Shawn Heisey wrote:
> On 11/18/2010 4:51 PM, Xymon User in Richmond wrote:
>> Not the same thing, but I had a situation where internal web servers
>> would
>> all go red a number of times a day then go green again on the next test.
>> No complaints from users, and I couldn't identify the network anomaly
>> causing it, so I just use "badhttp 2:3:4" for them in bb-hosts. They
>> pretty much stay in "smiley" green, but that's better than alarms for no
>> good purpose.
>>
>> It's "badTEST" in the manpage.
>
> Does this work for all tests, or does it only work for the built-in
> network tests? I have a couple of custom scripts that occasionally give
> false alarms.
>
IIRC it's only for the built-in network tests. That's implied but not
definitively stated in the manpage.