Escalations - getting a different message/notify command for each escalation level.
Stanley Hopcroft
Stanley.Hopcroft at IPAustralia.Gov.AU
Tue May 25 07:50:33 CEST 2004
On Mon, May 24, 2004 at 08:18:27PM -0700, nagios-users-request at lists.sourceforge.net wrote:
> From: Andreas Ericsson <ae at op5.se>
> To: Nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Escalations - getting a different message/notify
> command for each different escalation level.
>
> > Is there any way of having escalated notifications send a different
> > alert/notice message for each different escalation level ?
> >
> Yes. Nagios sports the nifty macro $NOTIFICATIONNUMBER$ (or something)
> which can be passed to notification-commands. Just write your own and
> evaluate the $NOTIFICATIONNUMBER$ macro before 'designing' the message.
>
> If this macro doesn't work as I expect (it might not, after all), then
> why not just add another macro ($ESCALATIONLEVEL$ or something).
>
> I have a script that could easily be hacked for this lying around
> somewhere, but I'm not sure where I've put it. I'll let you know if I
> find it.
>
> > A possible future solution would be to allow escalation templates to
> > specify the host_notify_command and service_notify_command attributes.
> >
> Seems like a bit overkill to me, since it would require more of both
> nagios and the end user. I'll dig in on finding that notification-script
> and make it public (maybe even default?) one way or another.
>
It seems to me that this proposal requires that the custom notification
command be used for _all_ notifications (at least those that want a
different message for each escalation level).
I would prefer that the custom notification command be used by only for
escalated notifications.
> > Another rather awkward solution is to have an event correlator examine
> > the Nag logs and use the correlators rules and actions to do the
> > escalation.
> >
(This was a rediculous proposal of mine since the correlator would have
to replicate the Nag configuration for
hosts/hostgroups/services/constacts .. to determine who gets notified.
Quite doable - epsesh with Nagios::Config but stupid).
> The notification command I wrote gets name of acknowledging user this
> way. Depending on the depth of mining you need to do, it's not really
> all that hard.
>
Thanks for your comments. Unfortunately, I don't see a way to do what I
want at the moment.
> Sourcerer / Andreas Ericsson
> OP5 AB
> +46 (0)733 709032
> andreas.ericsson at op5.se
--
------------------------------------------------------------------------
Stanley Hopcroft
------------------------------------------------------------------------
'...No man is an island, entire of itself; every man is a piece of the
continent, a part of the main. If a clod be washed away by the sea,
Europe is the less, as well as if a promontory were, as well as if a
manor of thy friend's or of thine own were. Any man's death diminishes
me, because I am involved in mankind; and therefore never send to know
for whom the bell tolls; it tolls for thee...'
from Meditation 17, J Donne.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
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
More information about the Users
mailing list