Wildcards in service escalations query

[Mohit Chawla]

Hi,

On Wed, Jul 6, 2011 at 2:08 AM, Paul M. Dubuc <work at paul.dubuc.org> wrote:
> It could be that the exclusion (!) doesn't work when combined with the *
> wildcard in that way.  It's equivalent to "host1, host2, ... hostN, !host1,
> !host2".  Try putting the wildcard at the end of the list and see if that
> works.

Nope, that doesn't change the behavior.

> Also, make sure that the hosts you exclude are really the only ones
> that have no services.  Nagios will put warnings in the log file about hosts
> with no services assigned after it is restarted.  You can look there for any
> you might have missed.

I expected this, but it isn't happening either. It doesn't log
warnings for these hosts, not even the ones I have _confirmed_ that
have no services associated.

------------------------------------------------------------------------------
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