When looking at an availability report generated by avail.cgi, I notice that my
stats are way off if a service goes critical and someone then schedules
downtime for a service. I expect that downtime should not be counted as
critical because it would mean that it's because of a planned activity such as
maintenance.
For example, I have:
07-28-2012 00:00:00 07-28-2012 03:05:06 0d 3h 5m 6s SERVICE OK
(HARD) OK - 167 results in 5.318780151 seconds
07-28-2012 03:05:06 07-28-2012 03:21:05 0d 0h 15m 59s SERVICE
CRITICAL (HARD) (Service Check Timed Out)
07-28-2012 03:21:05 07-28-2012 03:41:04 0d 0h 19m 59s SERVICE
DOWNTIME START Start of scheduled downtime
07-28-2012 03:41:04 07-29-2012 00:00:00 0d 20h 18m 56s SERVICE
DOWNTIME END End of scheduled downtime
07-29-2012 00:00:00 07-29-2012 04:21:11 0d 4h 21m 11s SERVICE OK
(HARD) OK - 167 results in 5.235716141 seconds
In this example, Nagios is showing me over 9 hours of critical time because the
service was in a critical state when it entered the downtime, which lasted for
9 hours. I've played around with all of the state options, but nothing seems
to help. Can anything be done to fix this?
Thanks
John Alberts
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
