Page 1 of 1

Critical alert sent during not-in-service time

Posted: Wed Jan 16, 2019 12:39 pm
by Bitflogger
Service_notifications.png
Service_state_history.png
Service_notifications.png
Hello,

I'm running V5.5.8, 64-bit, VM. CentOS 7.

We did an MS update on a large number of servers this morning. The servers have time periods that mask out a 40 minute time period.

Many servers had their updates and there were no unexpected alert.

A few servers had problems. I'll use an example that had a time period for update at 3:00 AM to 3:40.

I verified the server date/time is correct.

A critical state was recorded, a critical alert was sent at 3:20.

A normal state existed later, but the state change does not appear in the state history, and no recovery alert was sent.

Re: Critical alert sent during not-in-service time

Posted: Wed Jan 16, 2019 3:17 pm
by scottwilkerson
Can you verify the timeperiod for this service in the CCM and send the config definitions for that timeperiod?

Re: Critical alert sent during not-in-service time

Posted: Wed Jan 16, 2019 4:08 pm
by Bitflogger
Hello,

It is:

[ead@winston hosts]$ cat brother.doit.wisc.edu.cfg
###############################################################################
#
# Host configuration file
#
# Created by: Nagios Core Config Manager 2.6.11
# Date: 2018-05-09 10:31:18
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################

define host {
host_name brother.doit.wisc.edu
use windows-server
address brother.doit.wisc.edu
contact_groups se-windows
notification_period win_wed_0300
register 1
}

###############################################################################
#
# Host configuration file
#
# END OF FILE
#
###############################################################################
[ead@winston hosts]$

define timeperiod {
timeperiod_name win_wed_0300
alias Automatic Updates - Wednesday - 03:00
sunday 00:00-24:00
monday 00:00-24:00
tuesday 00:00-24:00
wednesday 00:00-02:55,03:40-24:00
thursday 00:00-24:00
friday 00:00-24:00
saturday 00:00-24:00
}

Re: Critical alert sent during not-in-service time

Posted: Wed Jan 16, 2019 5:13 pm
by scottwilkerson
Is this same timeperiod applied to the service?

Re: Critical alert sent during not-in-service time

Posted: Wed Jan 16, 2019 6:23 pm
by Bitflogger
Hello,

The service was 24x7.

I thought the host notification period overruled the service.

Even if that is not true, the normal state was missing from the service state history, after the critical state.

Earl

Re: Critical alert sent during not-in-service time

Posted: Thu Jan 17, 2019 8:40 am
by scottwilkerson
Bitflogger wrote:I thought the host notification period overruled the service.
No, services are independent
Bitflogger wrote:Even if that is not true, the normal state was missing from the service state history, after the critical state.
For the State history report set the State Type to "Both"

Re: Critical alert sent during not-in-service time

Posted: Thu Jan 17, 2019 9:47 am
by Bitflogger
Thanks Scott!

Please lock the case.

Earl

Re: Critical alert sent during not-in-service time

Posted: Thu Jan 17, 2019 10:10 am
by scottwilkerson
Bitflogger wrote:Thanks Scott!

Please lock the case.

Earl
Great Locking