Linux – Nagios escalation and wildcards

linuxmonitoringnagios

I've problems configuring escalations on nagios. I'm getting a the following error:

Error: Could not expand hostgroups and/or hosts specified in host escalation (config file '/usr/local/nagios/etc/objects/escalations.cfg', starting on line 11)
   Error processing object config files!

The escalations.cfg file looks as follow:

define hostescalation{
  host_name    *
  contact_groups    admins
  first_notification  1
  last_notification  3
  notification_interval  30
  escalation_period  24x7
  escalation_options  d,u
  }

define hostescalation{
  host_name    *
  contact_groups    suppliers
  first_notification  4
  last_notification  6
  notification_interval  60
  escalation_period  24x7
  escalation_options  d,u
  }

define serviceescalation{
  host_name    script.myprojects
  service_description  HTTP
  first_notification  1
  last_notification  3
  notification_interval  30
  contact_groups    admins
  }

define serviceescalation{
  host_name    script.myprojects
  service_description  HTTP
  first_notification  4
  last_notification  6
  notification_interval  60
  contact_groups    suppliers
  }

What I want is, get all hostgroups and their members using the wildcard (*). This is not working. Can anyone provide any solution? Am I missing any definition and if so, where/how to put this definition?

Thanks!

Best Answer

It's not clear whether you can use wildcards in this object definition. But assuming you can, make sure you have use_regexp_matching=0 per this Nagios doc: http://nagios.sourceforge.net/docs/3_0/configmain.html#use_regexp_matching

Related Solutions

Nagios (Last Notification: N/A (notification 0))

I don't see it mentioned in your question or any of the answers but have you checked the nagios.cfg file for the enable_notifications setting? Is it set to 0 or 1?

Also is this only happening on a given service notification or is it affecting all notifications? If it's all I would suspect that enable_notifications is set to 0 in the nagios.cfg file. If so try changing it to 1 and restarting Nagios.

Nagios Notification Escalation

I think it would work if you specified the time period on the contact. Define the contact twice: once with notifications at night, and again with notifications only during the day.

define service{
    use                             generic-service
    host_name                       mercury
    service_description             ROB_TEST2
    check_command                   check_pop
    contacts                        rob_daytime, rob_nighttime
    }

define serviceescalation{
    host_name                       mercury
    service_description             ROB_TEST2
    first_notification              3
    last_notification               5
    notification_interval           30
    contacts                        rob_daytime, rob_nighttime
    }

define serviceescalation{
    host_name                       mercury
    service_description             ROB_TEST2
    first_notification              6
    last_notification               9999
    notification_interval           60
    contacts                        rob_daytime
    }

define contact{
    contact_name                    rob_daytime
    service_notification_period daytime
    ...
    }

define contact{
    contact_name                    rob_nighttime
    service_notification_period nighttime
    ...
    }

This should give you a good night's sleep even though an escalation has been running for a few days.

Note: I haven't tested this myself ;-)

Related Topic