Passive problems not showing as "unhandled"

Engage with the community of users including those using the open source solutions.
Includes Nagios Core, Plugins, and NCPA

Passive problems not showing as "unhandled"

Postby nozlaf » Wed Aug 24, 2016 4:26 pm

Nagios 4.1.1

I've noticed that if you click on Services (Unhandled) any service with active checks disabled and passive checks enabled if the service has a warning or critical state generated from a passive check it is not listed on the unhandled screen despite it sending notifications for the status of the service being warning or critical

butit does appear if you click Problems or Services


I am 80% sure 3.x didn't operate this way

its certainly not how I would expect it to work

is this the expected behavior ?
Looking forward to seeing you all at #NagiosCon2019?
-Dedicated Lover of Nconf,PNP4Nagios and Nagvis
User avatar
nozlaf
 
Posts: 172
Joined: Sun Nov 09, 2014 9:50 pm
Location: Victoria, Australia

Re: Passive problems not showing as "unhandled"

Postby eloyd » Wed Aug 24, 2016 4:40 pm

I can confirm that, despite the awkward wording of this report, that if you have a service with passive checks in a warning or critical state, they do not show up on the list of unhandled problems, but they do show up on the list of all problems. Nagios Core 4.1.1.
Image
Eric Loyd • http://everwatch.global • 844.240.EVER • @EricLoydI'm a Nagios Fanatic!
User avatar
eloyd
Cool Title Here
 
Posts: 2103
Joined: Thu Sep 27, 2012 9:14 am
Location: Rochester, NY

Re: Passive problems not showing as "unhandled"

Postby nozlaf » Thu Aug 25, 2016 4:34 am

yeah sorry i wrote it first thing in the morning after a late night and a couple of crying kids at ungodly hours,
must be a tough one because box293 has not answered
Looking forward to seeing you all at #NagiosCon2019?
-Dedicated Lover of Nconf,PNP4Nagios and Nagvis
User avatar
nozlaf
 
Posts: 172
Joined: Sun Nov 09, 2014 9:50 pm
Location: Victoria, Australia

Re: Passive problems not showing as "unhandled"

Postby lmiltchev » Thu Aug 25, 2016 2:17 pm

I was able to recreate the issue in Nagios Core 4.2.0, and posted the issue on GitHub:

https://github.com/NagiosEnterprises/nagioscore/issues/157
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
lmiltchev
QA Manager
 
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm


Return to Community Support

Who is online

Users browsing this forum: Google [Bot], majobenitez and 31 guests