Mass Immediate Check and passive service
Posted: Fri Aug 27, 2021 8:26 am
Hi,
In the Mass Immediate Check it's not possible to easily identified passive Service and I wondering if there is not a way to do it.
When we have issues on server, the sysadmin work on the problem to fixed it and then, go to the Mass Immediate Check to force check to see if the problem is solved by the Nagios point of view. But thesysadmin cannot identified easily the passive check and sometime force a check for a passive check. Thats generate out a alert since Fressness is configured to generate a warning and a ticket in our environnement.
If in the different view in the console, including Mass Immediate Check, it could be possible to identified the passive check, that would save alert for the support team. Is there a way to do that?
In the Mass Immediate Check it's not possible to easily identified passive Service and I wondering if there is not a way to do it.
When we have issues on server, the sysadmin work on the problem to fixed it and then, go to the Mass Immediate Check to force check to see if the problem is solved by the Nagios point of view. But thesysadmin cannot identified easily the passive check and sometime force a check for a passive check. Thats generate out a alert since Fressness is configured to generate a warning and a ticket in our environnement.
If in the different view in the console, including Mass Immediate Check, it could be possible to identified the passive check, that would save alert for the support team. Is there a way to do that?