[prev in list] [next in list] [prev in thread] [next in thread]
List: opennms-discuss
Subject: Re: [opennms-discuss] destinationPaths.xml
From: doug huneycutt <doug.huneycutt () gmail ! com>
Date: 2016-09-29 10:26:14
Message-ID: CAK4-KKVOMPo057z_OAQUbpD53JRQHnFOmFpZR_8Ww_H1gmYqKg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thank you for this explanation. I wish that all of the documentation I
read had half of the clarity, focus, and usefulness of your answer.
Thanks again,
Doug
On Thu, Sep 29, 2016 at 2:52 AM, Cyrille Bollu <cyrille.bollu@gmail.com>
wrote:
> Hi,
>
> You seem to correctly understand destination paths:
>
> - You shouldn't receive reminders if you're defined as a target only
> once.
> - To delay a notification for 5 minutes, you have to set an
> initial-delay of "5m".
>
> Maybe what you're missing is the correct destinationPath definition in
> your notifications (in file notifications.xml)?
>
> Here are 2 examples of our setup:
>
> Examples:
>
> 1) The following path will send 1 and only one email to user "Admin" if a
> notification whose destination path is "email-delayed" has been triggered
> for more than 5 minutes:
>
> <path name="email-delayed" initial-delay="5m">
> <target interval="0s">
> <name xmlns="">Admin</name>
> <command xmlns="">javaEmail</command>
> </target>
> </path>
>
> 2) The following path will send 1 email to user "Admin" direcly when a
> notification whose destination path is "major-problem" has been triggered,
> 1 SMS to user "support" 5 minutes later, another SMS, as reminder, to user
> "support" yet 15 minutes later, yet another reminder SMS 20 minutes later,
> and finaly, a last SMS 60 minutes after the notification got triggered:
>
> <path name="major-problem" initial-delay="0s">
> <target interval="0s">
> <name xmlns="">Admin</name>
> <command xmlns="">javaEmail</command>
> </target>
> <escalate delay="5m">
> <target>
> <name xmlns="">support</name>
> <command xmlns="">sms-guard</command>
> </target>
> </escalate>
> <escalate delay="15m">
> <target>
> <name xmlns="">support</name>
> <command xmlns="">sms-guard</command>
> </target>
> </escalate>
> <escalate delay="20m">
> <target>
> <name xmlns="">support</name>
> <command xmlns="">sms-guard</command>
> </target>
> </escalate>
> <escalate delay="20m">
> <target>
> <name xmlns="">support</name>
> <command xmlns="">sms-guard-coord</command>
> </target>
> </escalate>
> </path>
>
> 3) Here's an example of 3 notifications using the destination paths
> described here above:
>
> <!-- Please respect the order of the following 3 notifications -->
> <notification name="CriticalNodeDown" status="on" writeable="yes">
> <uei>uei.opennms.org/nodes/nodeDown</uei>
> <rule>( notifyCategory LIKE 'Critical%' )</rule>
> <destinationPath>major-problem</destinationPath>
> <text-message>All services are down on node %nodelabel%
> (CRITICAL). New Outage records have
> been created and service level availability calculations will
> be impacted until this outage is resolved.
> </text-message>
> <subject>Notice #%noticeid%: node %nodelabel% down.</subject>
> <numeric-message>111-%noticeid%</numeric-message>
> </notification>
> <notification name="NonCriticalNodeDown" status="on" writeable="yes">
> <uei>uei.opennms.org/nodes/nodeDown</uei>
> <rule>( notifyCategory == 'LowCriticality' )</rule>
> <destinationPath>email-delayed</destinationPath>
> <text-message>All services are down on node %nodelabel%
> (non-critical). New Outage records have
> been created and service level availability calculations will
> be impacted until this outage is resolved.
> </text-message>
> <subject>Notice #%noticeid%: node %nodelabel% down.</subject>
> <numeric-message>111-%noticeid%</numeric-message>
> </notification>
> <notification name="nodeDown" status="on" writeable="yes">
> <uei>uei.opennms.org/nodes/nodeDown</uei>
> <rule>IPADDR != '0.0.0.0'</rule>
> <destinationPath>email</destinationPath>
> <text-message>All services are down on node %nodelabel%. New
> Outage records have
> been created and service level availability calculations will
> be impacted until this outage is resolved.
> </text-message>
> <subject>Notice #%noticeid%: node %nodelabel% down.</subject>
> <numeric-message>111-%noticeid%</numeric-message>
> </notification>
>
> Regards,
>
> Cyrille
>
> 2016-09-27 20:37 GMT+02:00 rbacon <rbacon@indigowireless.com>:
>
>> I have found a lot of post here for this file and if I missed the 1 that
>> I am
>> asking I am sorry.
>>
>>
>> We have a problem on our network where people keep turning things on and
>> off
>> and I am getting alarms non stop. I know with this file I should be able
>> to
>> delay the message from being sent until the device is down for x amount of
>> minutes. I am however not seeing this work. I have 2 paths set up
>>
>> path 1
>> initial delay = 1m
>> target interval = 1m
>> path 2
>> initial delay = 1m
>> target interval = 1m
>>
>> I would like a 5 minute buffer so if a device is down for more than 5
>> minutes I get a message it is down. I want another message once it is up
>> and
>> no reminders.... EVER. Because of what is being monitored some things
>> might
>> be down for a month but we what to know when its up/down.
>>
>> Thank you!
>>
>>
>>
>>
>> --
>> View this message in context: http://opennms.530661.n2.nabbl
>> e.com/destinationPaths-xml-tp7594253.html
>> Sent from the OpenNMS - discuss mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------
>> ------------------
>> _______________________________________________
>> Please read the OpenNMS Mailing List FAQ:
>> http://www.opennms.org/index.php/Mailing_List_FAQ
>>
>> opennms-discuss mailing list
>>
>> To *unsubscribe* or change your subscription options, see the bottom of
>> this page:
>> https://lists.sourceforge.net/lists/listinfo/opennms-discuss
>>
>
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss
>
[Attachment #5 (text/html)]
<div dir="ltr">Thank you for this explanation. I wish that all of the documentation \
I read had half of the clarity, focus, and usefulness of your \
answer.<div><br></div><div>Thanks again,</div><div>Doug</div><div><br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 29, 2016 at 2:52 AM, \
Cyrille Bollu <span dir="ltr"><<a href="mailto:cyrille.bollu@gmail.com" \
target="_blank">cyrille.bollu@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div \
dir="ltr"><div><div><div><div><div>Hi,<br><br></div><div>You seem to correctly \
understand destination paths:</div><ul><li>You shouldn't receive reminders if \
you're defined as a target only once.</li><li>To delay a notification for 5 \
minutes, you have to set an initial-delay of "5m".</li></ul></div>Maybe \
what you're missing is the correct destinationPath definition in your \
notifications (in file notifications.xml)?<br><br></div><div>Here are 2 examples of \
our setup:<br><br></div>Examples:<br><br>1) The following path will send 1 and only \
one email to user "Admin" if a notification whose destination path is \
"email-delayed" has been triggered for more than 5 minutes:<br><br> \
<path name="email-delayed" initial-delay="5m"><br> \
<target interval="0s"><br> <name \
xmlns="">Admin</name><br> <command \
xmlns="">javaEmail</command><br> </target><br> \
</path><br><br></div>2) The following path will send 1 email to user \
"Admin" direcly when a notification whose destination path is \
"major-problem" has been triggered, 1 SMS to user "support" 5 \
minutes later, another SMS, as reminder, to user "support" yet 15 minutes \
later, yet another reminder SMS 20 minutes later, and finaly, a last SMS 60 minutes \
after the notification got triggered:<br><br> <path \
name="major-problem" initial-delay="0s"><br> \
<target interval="0s"><br> <name \
xmlns="">Admin</name><br> <command \
xmlns="">javaEmail</command><br> </target><br> \
<escalate delay="5m"><br> <target><br> \
<name xmlns="">support</name><br> \
<command xmlns="">sms-guard</command><br> \
</target><br> </escalate><br> <escalate \
delay="15m"><br> <target><br> \
<name xmlns="">support</name><br> \
<command xmlns="">sms-guard</command><br> \
</target><br> </escalate><br> <escalate \
delay="20m"><br> <target><br> \
<name xmlns="">support</name><br> \
<command xmlns="">sms-guard</command><br> \
</target><br> </escalate><br> <escalate \
delay="20m"><br> <target><br> \
<name xmlns="">support</name><br> \
<command xmlns="">sms-guard-coord</comm<wbr>and><br> \
</target><br> </escalate><br> \
</path><br><br></div>3) Here's an example of 3 notifications using the \
destination paths described here above:<br><br><div><!-- Please respect the order \
of the following 3 notifications --><br> <notification \
name="CriticalNodeDown" status="on" \
writeable="yes"><br> <uei><a \
href="http://uei.opennms.org/nodes/nodeDown" \
target="_blank">uei.opennms.org/nodes/nod<wbr>eDown</a></uei><br> \
<rule>( notifyCategory LIKE 'Critical%' )</rule><br> \
<destinationPath>major-problem<wbr></destinationPath><br> \
<text-message>All services are down on node %nodelabel% (CRITICAL). New \
Outage records have<br>been created and service level availability calculations \
will<br>be impacted until this outage is resolved.<br> \
</text-message><br> <subject>Notice #%noticeid%: node \
%nodelabel% down.</subject><br> \
<numeric-message>111-%noticeid<wbr>%</numeric-message><br> \
</notification><br> <notification name="NonCriticalNodeDown" \
status="on" writeable="yes"><br> <uei><a \
href="http://uei.opennms.org/nodes/nodeDown" \
target="_blank">uei.opennms.org/nodes/nod<wbr>eDown</a></uei><br> \
<rule>( notifyCategory == 'LowCriticality' )</rule><br> \
<destinationPath>email-delayed<wbr></destinationPath><br> \
<text-message>All services are down on node %nodelabel% (non-critical). New \
Outage records have<br>been created and service level availability calculations \
will<br>be impacted until this outage is resolved.<br> \
</text-message><br> <subject>Notice #%noticeid%: node \
%nodelabel% down.</subject><br> \
<numeric-message>111-%noticeid<wbr>%</numeric-message><br> \
</notification><br> <notification name="nodeDown" \
status="on" writeable="yes"><br> <uei><a \
href="http://uei.opennms.org/nodes/nodeDown" \
target="_blank">uei.opennms.org/nodes/nod<wbr>eDown</a></uei><br> \
<rule>IPADDR != '0.0.0.0'</rule><br> \
<destinationPath>email</destin<wbr>ationPath><br> \
<text-message>All services are down on node %nodelabel%. New Outage records \
have<br>been created and service level availability calculations will<br>be impacted \
until this outage is resolved.<br> </text-message><br> \
<subject>Notice #%noticeid%: node %nodelabel% down.</subject><br> \
<numeric-message>111-%noticeid<wbr>%</numeric-message><br> \
</notification><br><br></div><div>Regards,<br><br></div><div>Cyrille<br></div></div><div \
class="gmail_extra"><br><div class="gmail_quote">2016-09-27 20:37 GMT+02:00 rbacon \
<span dir="ltr"><<a href="mailto:rbacon@indigowireless.com" \
target="_blank">rbacon@indigowireless.com</a>></span>:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">I have found a lot of post here for this file and if I missed \
the 1 that I am<br> asking I am sorry.<br>
<br>
<br>
We have a problem on our network where people keep turning things on and off<br>
and I am getting alarms non stop. I know with this file I should be able to<br>
delay the message from being sent until the device is down for x amount of<br>
minutes. I am however not seeing this work. I have 2 paths set up<br>
<br>
path 1<br>
initial delay = 1m<br>
target interval = 1m<br>
path 2<br>
initial delay = 1m<br>
target interval = 1m<br>
<br>
I would like a 5 minute buffer so if a device is down for more than 5<br>
minutes I get a message it is down. I want another message once it is up and<br>
no reminders.... EVER. Because of what is being monitored some things might<br>
be down for a month but we what to know when its up/down.<br>
<br>
Thank you!<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a \
href="http://opennms.530661.n2.nabble.com/destinationPaths-xml-tp7594253.html" \
rel="noreferrer" target="_blank">http://opennms.530661.n2.nabbl<wbr>e.com/destinationPaths-xml-tp7<wbr>594253.html</a><br>
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.<br>
<br>
------------------------------<wbr>------------------------------<wbr>------------------<br>
______________________________<wbr>_________________<br>
Please read the OpenNMS Mailing List FAQ:<br>
<a href="http://www.opennms.org/index.php/Mailing_List_FAQ" rel="noreferrer" \
target="_blank">http://www.opennms.org/index.p<wbr>hp/Mailing_List_FAQ</a><br> <br>
opennms-discuss mailing list<br>
<br>
To *unsubscribe* or change your subscription options, see the bottom of this \
page:<br> <a href="https://lists.sourceforge.net/lists/listinfo/opennms-discuss" \
rel="noreferrer" target="_blank">https://lists.sourceforge.net/<wbr>lists/listinfo/opennms-discuss</a><br>
</blockquote></div><br></div>
<br>------------------------------<wbr>------------------------------<wbr>------------------<br>
<br>______________________________<wbr>_________________<br>
Please read the OpenNMS Mailing List FAQ:<br>
<a href="http://www.opennms.org/index.php/Mailing_List_FAQ" rel="noreferrer" \
target="_blank">http://www.opennms.org/index.p<wbr>hp/Mailing_List_FAQ</a><br> <br>
opennms-discuss mailing list<br>
<br>
To *unsubscribe* or change your subscription options, see the bottom of this \
page:<br> <a href="https://lists.sourceforge.net/lists/listinfo/opennms-discuss" \
rel="noreferrer" target="_blank">https://lists.sourceforge.net/<wbr>lists/listinfo/opennms-discuss</a><br></blockquote></div><br></div></div>
------------------------------------------------------------------------------
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-discuss mailing list
To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic