Wildcards in service escalations query
Mohit Chawla
mohit.chawla.binary at gmail.com
Tue Jul 5 21:28:06 CEST 2011
Hi,
On Tue, Jul 5, 2011 at 11:55 PM, Paul M. Dubuc <work at paul.dubuc.org> wrote:
> As long as any hosts that match the host_name directive have no services
> defined, you will get this error. The escalation apparently wants to have
> host/service pairs. It's a service escalation and all services must be
> assigned to a host. It doesn't automatically discard hosts that have no
> services.
But as you can see in the above config I posted, I am explicitly
excluding those hosts which do not have any services associated with
them ( foo.com and bar.com ). Hence, the config should be valid.
Unless ofcourse: host_name *. !host1, !host2 is not the right way to
include all hosts except host1 and host2 or some other bad logic.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Nagios-users mailing list
Nagios-users at 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
More information about the Users
mailing list