Can't clear "Critical" service status summary

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
bjohnon6030
Posts: 2
Joined: Wed Jun 29, 2016 7:32 am

Can't clear "Critical" service status summary

Post by bjohnon6030 »

I have sticky acknowledged all the critical errors we had listed under "Services", however in the service status summary the "critical" error number has not changed. Aside from manually turning off each individual service, is there any way for me to clear this number?
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Can't clear "Critical" service status summary

Post by rkennedy »

Can you show us a screenshot of what you're trying to clear? You could send a passive check as 'OK' to 'clear' it, but if the check renews and it's still in a critical state then it will go right back.
Former Nagios Employee
bjohnon6030
Posts: 2
Joined: Wed Jun 29, 2016 7:32 am

Re: Can't clear "Critical" service status summary

Post by bjohnon6030 »

The 180 critical errors are almost all unused ports which have been sticky acknowledged. However we would like to see that critical error number drop as well, so that we can see exactly how many actual critical errors there are. The only way so far I have been able to do this is to manually turn off each service. But then we would have to turn them back on when we want to utilize those ports. Either way it's not a huge deal but we were wondering if there was another way to accomplish this. Thank you so much for your help.
You do not have the required permissions to view the files attached to this post.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Can't clear "Critical" service status summary

Post by rkennedy »

If you used the wizard, you can change the command for check_xi_service_ifoperstatus, but keep in mind this will turn all criticals for that check to OK. You won't receive the correct information or notification if an interface goes critical (that previously wasn't), so keep that in mind. We'll use the negate plugin, to change all the CRITICAL -> OK.

Change it to -

Code: Select all

$USER1$/negate -c OK $USER1$/check_ifoperstatus -H $HOSTADDRESS$ -C $ARG1$ -k $ARG2$ $ARG3$
Former Nagios Employee
Locked