Bob Ingraham wrote:
> Question for the list:
>
> While working on documenting the NEB interface and the various interal
> Nagios data structures for our delevopment team, I came across this issue
> with Soft OK states.
>
> Is this a valid state? We've had one instance where a service was in a
> Soft Critical state for two attempts, then the service was restored and
> the log (and availability report) start showing a Soft OK state (3rd
> attempt).
>
> This screwed-up our availability report for this service, since the
> service recovered after 20 minutes, but the availability report shows 16
> hours of downtime (because, 16 hours later, the logs were rotated at
> midnight and the state was reset to "Hard" OK.)
>
> So, again, is this by design or is it a bug?
>
> BTW, we've seen this behavior on both our current Nagios 2.2 version and
> an ancient Nagios 1.1 version that's going to be retired shortly.
>
> Thanks,
> Bob
>
This is actually a feature. A service that recovers to an OK state
before reaching a HARD problem state, will be considered a "SOFT"
recovery. If the next check of the service returns an OK state, the
service state type will be reset to "HARD".
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]