On 12/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] schrieb am 12.12.2005 16:22:34:
>
> > I am using Nagios 2.0b6, but also experienced this issue in 2.0b4.
> > Nagios escalations do not seem to work when the state changes after a
> > maximum notifications level has been reached. For example, if a
>
> You are mislead. Your escalations are only defined up to
> notification 5, at notification 6 they end and Nagios reverts
> to the base definition of the service.
>
> > define hostescalation{
> > host_name test-server
> > first_notification 5
> > last_notification 5
> > notification_interval 0
> > contact_groups oncall,backup
> > }
> >
> > define serviceescalation{
> > host_name test-server
> > service_description /MYSQL
> > first_notification 5
> > last_notification 5
> > notification_interval 0
> > contact_groups oncall,backup
> > }
> >
> > Please let me know if I need to include more information. Thanks in
> advance.
>
> Changing last_notification to 0 in those cases should
> produce your desired effect if I did understand you
> correctly.
>
So I would need to have last_notification be 0 and
notification_interval be 0? Or just last_notification? Is there a
better way for me to do the service escalation so I do not have 3
separate entries? I do know that you can have similar services from
multiple hosts in the same service escalation, but I am just wondering
if I can compress the configs a little more. Thanks for the quick
response.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users@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
