Page 1 of 1
Passive Checks & State
Posted: Mon Dec 09, 2019 2:37 pm
by cstuart
Hello - I was wondering if we could submit a feature request to be able to treat critical statuses on passive checks as soft until they've been critical for X seconds.
Re: Passive Checks & State
Posted: Mon Dec 09, 2019 3:12 pm
by lmiltchev
Hmm, what's wrong with using the max_check_attempts directive?
In order to prevent false alarms from transient problems, Nagios Core allows you to define how many times a service or host should be (re)checked before it is considered to have a "real" problem. This is controlled by the max_check_attempts option in the host and service definitions.
Soft states occur in the following situations:
* When a service or host check results in a non-OK or non-UP state and the service check has not yet been (re)checked the number of times specified by the max_check_attempts directive in the service or host definition. This is called a soft error.
* When a service or host recovers from a soft error. This is considered a soft recovery.
https://assets.nagios.com/downloads/nag ... types.html
Re: Passive Checks & State
Posted: Mon Dec 09, 2019 3:55 pm
by cstuart
I'll be happy if I misunderstood. I thought max_check_attempts was only for active checks.
If I can use that, it would be a start. There might also be passive checks that don't come in on a regular interval, so setting a max_check_attempts might not accurately dictate when there's a real problem. It would be very helpful to be able to specify an amount of time.
Re: Passive Checks & State
Posted: Mon Dec 09, 2019 4:27 pm
by lmiltchev
My bad, somehow I missed the fact that you were talking about passive checks...
This functionality doesn't exist in Nagios Core. You are welcome to file a feature request here:
https://github.com/NagiosEnterprises/nagioscore/issues
Please keep in mind that the decision to implement the enhancement is at the discretion of our development team. Thank you!