Re: [Nagios-users] Differentiate receivers based on alert severity?

[Ruslan V. <lin...@gm...>]

Does it mean I have to create two different service templates and specify
my emails there?


On Mon, Jul 30, 2012 at 11:13 AM, Assaf Flatto <na...@fl...> wrote:

> **
> Yes , you can use two different contacts , one that has only warning , and
> the other only for critical .
>
>
>
>
> On 30/07/12 09:54, Ruslan Valiyev wrote:
>
> Hi,
>
>  I was wondering if it's possible to achieve something a la:
>
>  - when CPU alerts are warning, they should go to us...@fo...
> - when CPU alerts are critical, they should go to us...@fo...
>
>
>  Ruslan
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Nagios-users mailing lis...@li...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
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Nagios-users mailing list
> Nag...@li...
> 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
>