On 10/07/18 19:55, Edgar Fuß wrote:
In order to move to a hard non-ok state, a service can require multiple (i.e.
max_check_attempts) unsuccessful runs of the check plugin.
Is there a way to require multiple successful plugin runs in order to return to
a (hard) ok state?
I have printers where,
Looking at the Icinga 1.x documentation ("5.8.4 Hard states",
https://www.icinga.com/docs/icinga1/latest/en/statetypes.html#hardstates)
it says:
Hard states occur for hosts and services in the following situations:
*
When a host or service check results in a non-UP or non-OK state and
So you are using separate cluster-zone service check?
What are you using for the host check?
Rick
From: icinga-users on behalf of mustafa
mujahid
Sent: July 10, 2018 7:16 AM
To: Icinga User's Corner
Subject: Re: [icinga-users] Distributed Monitoring for Cli
In order to move to a hard non-ok state, a service can require multiple (i.e.
max_check_attempts) unsuccessful runs of the check plugin.
Is there a way to require multiple successful plugin runs in order to return to
a (hard) ok state?
I have printers where, if toner is low (not empty), from time
This is a valid question to which I was also looking for the answer. If the
zone disconnects then only the cluster zone service fails. When it should
trigger the RED for all services in that zone. It doesn’t happen. I guess
dependency checks can be used but I’m not sure.
BR/Mustafa.
Sent from
