Hi Steve,
That decision was made a while ago and I probably though about using the
freshness checking. I guess my idea was that a trap should stay on until it is
handled.
For various reasons we're not really using traps yet, but the system is there
for the day we start using them (soon hopefully). Maybe after we use them a bit
we'll decide on changing to "Self-reset" traps. Thanks for bringing is on
though, that's a good suggestion... :)
Thomas
-----Original Message-----
From: Steve Shipway [mailto:[EMAIL PROTECTED]
Sent: Tue 13-Mar-07 19:51
To: Thomas Guyot-Sionnest; [email protected]
Subject: RE: [Nagios-users] Trap reset script
> It will look up the status and command files from the Nagios config,
parse
> the status and then force an active check for services matching these
> criterias:
> 1. Should not be scheduled to be checked
> 2. Has active checks enabled
Is there a reason why you are not using the Nagios freshness checking to
achieve this?
We have a similar system, with SNMP alerts coming into Nagios, and use
the Freshness Check to set the status to OK after a set period of time.
Services are set to volatile, max_checks=1, so they notify immediately
on receiving a trap no matter what the current state.
Steve
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
