Hallo all,
The usecase I was writing about does work if and only if the exclude is
defined to exact service's name. Negative regular expressions do not work
in 1.9.2 apparently.
And yes, regexps are enabled in config, but not full regexp.
I'm going to test this usecase with newest 1.10 too.
Regards, .zp.
On Nov 1, 2013 11:57 PM, "Michael Friedrich" <michael.friedr...@gmail.com>
wrote:
> On 23.10.2013 17:15, Zdenek Pizl wrote:
> > Hallo,
> >
> > Let's say I have following configuration:
> >
> > define serviceescalation {
> > hostgroup_name CPP
> > service_description .*
> > first_notification 1
> > last_notification 0
> > notification_interval 0
> > contact_groups CPP-CONTACTGRP
> > }
> >
> > define serviceescalation {
> > hostgroup_name CPP
> > service_description RootFS.*
> > first_notification 1
> > last_notification 0
> > notification_interval 0
> > contact_groups SYSTEM-CONTACTGRP
> > }
> >
> >
> > I cannot change definition neither of the services nor of the
> > hostgroups. According to this definition there will be TWO escalation
> > emails, to CPP-CONTACTGRP and SYSTEM-CONTACTGRP.
> >
> > Is there any way how to exclude 'RootFS.*' service from the first
> > definition? Following does not work:
> >
> > define serviceescalation {
> > hostgroup_name CPP
> > service_description .*,!RootFS.*
> > first_notification 1
> > last_notification 0
> > notification_interval 0
> > contact_groups CPP-CONTACTGRP
> > }
>
> that looks like a mix of exclusion and regular expression matching. do
> you have regexp enabled for your configuration? other than that, i'm not
> aware of service attribute exclusions in service escalations, only for
> host(group)s.
>
> >
> >
> > Any suitable solution? Thank you very much, regards .zp.
> >
> > --
> >
> > Zdenek Pizl
> > zdenek.p...@gmail.com <mailto:zdenek.p...@gmail.com>
> >
> >
> >
> ------------------------------------------------------------------------------
> > October Webinars: Code for Performance
> > Free Intel webinars can help you accelerate application performance.
> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> > the latest Intel processors and coprocessors. See abstracts and register
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> >
> >
> > _______________________________________________
> > icinga-users mailing list
> > icinga-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/icinga-users
>
>
> --
> DI (FH) Michael Friedrich
>
> mail: michael.friedr...@gmail.com
> twitter: https://twitter.com/dnsmichi
> jabber: dnsmi...@jabber.ccc.de
> irc: irc.freenode.net/icinga dnsmichi
>
> icinga open source monitoring
> position: lead core developer
> url: https://www.icinga.org
>
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/icinga-users
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
