Multiple wildcard (regex) definitions in serviceescalation
Posted: Fri Aug 20, 2010 3:07 pm
Good day all! I have a bit of a curious question. I have inherited a nagios2 install (yep, a bit old) and while it has the following serviceescalation definition:
define serviceescalation{
host_name *
service_description *
first_notification 2
last_notification 3
notification_interval 20
contact_groups secondary-oncall-group
}
I doubt it has ever worked, as use_regexp_matching was always set to '0'.
However, after turning on use_regexp_matching, I noticed that the config bombs with the following:
<snip>
Error: Could not find any host matching '*'
Error: Could not expand hostgroups and/or hosts specified in host escalation (config file '/etc/nagios/sm_master_escalation.cfg', starting on line 39)
</snip>
Is it possible that the existence of wildcards being defined for both host_name AND service_description is the issue?
If so, is it possible to set a system-wide (global) escalation policy for All hosts and All services?
Thanks in advance!
define serviceescalation{
host_name *
service_description *
first_notification 2
last_notification 3
notification_interval 20
contact_groups secondary-oncall-group
}
I doubt it has ever worked, as use_regexp_matching was always set to '0'.
However, after turning on use_regexp_matching, I noticed that the config bombs with the following:
<snip>
Error: Could not find any host matching '*'
Error: Could not expand hostgroups and/or hosts specified in host escalation (config file '/etc/nagios/sm_master_escalation.cfg', starting on line 39)
</snip>
Is it possible that the existence of wildcards being defined for both host_name AND service_description is the issue?
If so, is it possible to set a system-wide (global) escalation policy for All hosts and All services?
Thanks in advance!