Contact x One notification only

[Martin Melin]

Hello,

Please reply to the list so that everyone can benefit from the answers.

Simply define one escalation matching all services/hosts by using wildcards.
http://nagios.sourceforge.net/docs/3_0/objecttricks.html

Regards,
Martin Melin

On Mon, Oct 19, 2009 at 6:23 PM, Fernando - IT <faugusto.ti at gmail.com>wrote:

>    Hi Martin,
>
>   But I don't use escalations on my nagios configuration, is possible to
> configure a global escalation list? Because the definition say to config a
> escalation for each host/service, but the failure for all host/services will
> be treated for the same team.
>
> Thanks
>
> []'s
> Fernando
>
>
> On Mon, Oct 19, 2009 at 2:10 PM, Martin Melin <mmelin at gmail.com> wrote:
>
>> Hello,
>>
>> Use first_notification and last_notification in the escalation definition:
>> http://nagios.sourceforge.net/docs/3_0/escalations.html
>>
>> Regards,
>> Martin Melin
>>
>> On Mon, Oct 19, 2009 at 5:59 PM, Fernando - IT <faugusto.ti at gmail.com>wrote:
>>
>>>    Hi everybody,
>>>
>>>    I need a help to configure a contact to receive only one notification
>>> only. How I can do this configuration on Nagios?
>>>
>>> For example:
>>>
>>> Contact: Ticket.System at internal.inet
>>> Contact: Admin at internal.inet
>>>
>>> When a host/service goes down, I need to send notifications and
>>> repetitions normally for contact Admin, but for contact ticket.system I can
>>> only send a one notification, to be registered on my internal Ticket System.
>>>
>>> The same will be applied for warning, recovery, downtime, acknowledge,
>>> etc..
>>>
>>> Thanks a lot
>>>
>>> --
>>> []'s
>>> Fernando
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> 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
>>
>
>
>
> --
> []'s
> Fernando
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20091019/5a4aa9e7/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
-------------- next part --------------
_______________________________________________
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