Nagios alarm limit

Some unimportant alarms in the middle of the night will not affect the system and business, but no one will handle them until dawn is reported, fortunately, nagios provides an alarm extension vi/usr/local/nagios/etc/objects/escalations. includefine serviceescalation {host_name 192.168.1.1; names of the monitored Hosts, separated by commas. in cfg, www.2cto.com service_description SSH is consistent. The names of monitored services are separated by commas. consistent first_notification 4 in cfg; Starting from 4th messages, change frequency interval last_notification 0; Starting from n messages, recovery frequency interval icationication_interval 30; notification interval (unit: minute) contact_groups admins} define serviceescalation {host_name 192.168.1.1 service_description SSH first_notification 10 last_notification 0 icationication_interval 30 contact_groups boss}
Finally, edit nagios. cfg file www.2cto.com # vi/usr/local/nagios/etc/nagios. add: Export _file =/usr/local/nagios/etc/objects/escalations in cfg. cfg check whether the nagios configuration file is correct/usr/local/nagios/bin/nagios-v/usr/local/nagios/etc/nagios. if cfg is correct, restart the nagios service. service nagios restart indicates that an alarm is sent every 30 minutes from the first alarm to the admins group, after 10th, both the admins group and the boss group will receive the alarm time. The corresponding configuration file is used as the standard. In this example, the author gaoming655 is 30 minutes.