z

Commercial Support Clients: Clients with support contracts can get escalated support assistance by visiting Nagios Answer Hub. These forums are for community support services. Although we at Nagios try our best to help out on the forums here, we always give priority support to our support clients.

Nagios Core Summary Macro has Wrong Count

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.

Nagios Core Summary Macro has Wrong Count

Postby CarlosCarrancom » Wed Aug 31, 2022 2:27 am

I believe the following summary macros are not accounting for Passive Services: $TOTALSERVICESCRITICALUNHANDLED$ (This is the one with which I see the problem directly) And I assume the following two have the same issue: $TOTALSERVICESWARNINGUNHANDLED$ $TOTALSERVICESUNKNOWNUNHANDLED$ Passive Services who are NOT in downtime and NOT Acknowledged rightfully show up in the Unhandled Services page of Nagios Core. But, a script Im using spits out the value of $TOTALSERVICESCRITICALUNHANDLED$ that does not account for passive services who are non-downtime, non-ack, and in a critical state. The wordage on this macro indicates that the service must have 'checks enabled', but this probably does not account for passive checks?: " This macro reflects the total number of services that are currently in a CRITICAL state that are not currently being "handled". Unhandled services problems are those that are not acknowledged, are not currently in scheduled downtime, and for which checks are currently enabled. "

My setup: I have a command that is executed by a regularly scheduled service. The command passes the value of macro $TOTALSERVICESCRITICALUNHANDLED$ to a script. The script just echos the value of that macro.

Test: All services are in downtime except my passive service who has Passive Services Enabled and is in a critical state. The script is spitting out "0" for number of unhandled critical alerts (this is incorrect!) Enable active checks on the passive service and the script now tells me "1"

Nagios Core Version 4.3.2 Please advise whether this omegle.2yu.co is a bug that was addressed in a later version or whether there is any workaround for me? I have seen this related issue which was fixed in 4.2.2 but is a different omeglz echat issue: viewtopic.php?t=39957
CarlosCarrancom
 
Posts: 7
Joined: Thu May 05, 2022 7:02 am

Return to Open Source Nagios Projects

Who is online

Users browsing this forum: No registered users and 28 guests