Two Service Escalation Bugs
matthias eble
matthias.eble at mailing.kaufland-informationssysteme.com
Thu May 7 11:51:08 CEST 2009
On Wed, 2009-05-06 at 14:36 -0700, Mark Gius wrote:
> The second bug is an annoyance for me. When defining a service
> escalation, I found that the following escalation will generate _no_
> service escalations, and will not give any errors or warnings.
>
> define serviceescalation {
> hostgroup_name myHostgroup
> escalation_period workhours
> escalation_options c,u,r
> }
>
> My assumption for how this behaved was that it would match all
> services
> of the hostgroup.
I've stumbled over something similar yesterday. I defined a
servicedependency which simply didn't work. My mistake was that I set
the first notification flag, but not the last notification flag. Setting
the last_notification value to 0 solved my problem (which was what I
intended by omitting last_notifications). But I didn't dive in
xodtemplate stuff to fix this issue due to current situation.
HTH
Matthias
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
More information about the Developers
mailing list