Is there a recommended way to reset a monitor and clear an outage?
"Ostock,David J." <[email protected]> Tue, 27 Nov 2018 15:37:07 +0000
| Newsgroups | gmane.network.opennms.general |
|---|---|
| Message-ID | <SN6PR07MB4431808E192B00EDA1182D2CD6D00@SN6PR07MB4431.namprd07.prod.outlook.com> |
--===============0651060484454596193==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_SN6PR07MB4431808E192B00EDA1182D2CD6D00SN6PR07MB4431namp_"
--_000_SN6PR07MB4431808E192B00EDA1182D2CD6D00SN6PR07MB4431namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I forward OpenNMS alarms to a service management platform for trouble-ticke=
ting and have an occasional problem where a node-down outage occurs but a t=
icket doesn't get created.
I'd like to put a process in place that checks for that and resets the moni=
tor and clears the outage to allow the monitor to trigger again. I searche=
d the docs and the mailing lists, but couldn't find a way to do that.
I did some trial and error testing, but was not successful. Here's what I =
tried:
* Deleted the outage record from the outages table. That cleared the o=
utage, but the monitor doesn't trigger again even though the node is still =
down.
* Deleted the outage record and associated node-down event. Same as re=
sult as above.
* Set the ifregainedservice timestamp in the outage record to current t=
ime. Same as above.
Anyone have any idea how to do this?
Thanks,
Dave
--_000_SN6PR07MB4431808E192B00EDA1182D2CD6D00SN6PR07MB4431namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:302927957;
mso-list-type:hybrid;
mso-list-template-ids:-500026348 -1042500068 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I forward OpenNMS alarms to a service management pla=
tform for trouble-ticketing and have an occasional problem where a node-dow=
n outage occurs but a ticket doesn’t get created.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">I’d like to put a process in place that checks=
for that and resets the monitor and clears the outage to allow the monitor=
to trigger again. I searched the docs and the mailing lists, but cou=
ldn’t find a way to do that.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">I did some trial and error testing, but was not succ=
essful. Here’s what I tried:<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:-.25in;mso-list:l0 leve=
l1 lfo1">Deleted the outage record from the outages table. That clear=
ed the outage, but the monitor doesn’t trigger again even though the =
node is still down.<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"=
margin-left:-.25in;mso-list:l0 level1 lfo1">Deleted the outage record and a=
ssociated node-down event. Same as result as above.<o:p></o:p></li><l=
i class=3D"MsoListParagraph" style=3D"margin-left:-.25in;mso-list:l0 level1=
lfo1">Set the ifregainedservice timestamp in the outage record to current =
time. Same as above.<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Anyone have any idea how to do this?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Dave<o:p></o:p></p>
</div>
</body>
</html>
--_000_SN6PR07MB4431808E192B00EDA1182D2CD6D00SN6PR07MB4431namp_--
--===============0651060484454596193==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============0651060484454596193==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
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
--===============0651060484454596193==--