[prev in list] [next in list] [prev in thread] [next in thread]
List: opennms-discuss
Subject: Re: [opennms-discuss] "reason code" text now absent in "Log Msg" field in 20.0.1 breaks Advanced Sea
From: "Hernandez, Paul" <Paul_Hernandez () mentor ! com>
Date: 2017-08-10 19:38:35
Message-ID: bfc8d5ae8dee46ed8c8aa798542aab61 () svr-orw-mbx-01 ! mgc ! mentorg ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
Hi Marcel,
Well that is too bad, as we apparently threw the proverbial baby out with the \
bathwater for the sake of aesthetics. I do appreciate though that it is really hard \
to be aware of all the inter-dependencies in a tool this large.
Let's hope NMS-7676 happens soon then.
Regards,
Paul
From: Marcel Fuhrmann [mailto:mfuhrmann@mailbox.org]
Sent: Thursday, August 10, 2017 11:31 AM
To: General OpenNMS Discussion <opennms-discuss@lists.sourceforge.net>
Subject: Re: [opennms-discuss] "reason code" text now absent in "Log Msg" field in \
20.0.1 breaks Advanced Search
Hey Paul,
that sounds really ugly and I don't have a usable workaround.
To be honest... I initialized this change [1][2]... because it wasn't correct to have \
detailed information in the alarm title.
In some cases you got messages like this:
Postgres outage identified on interface 10.10.7.48 with reason code: JDBC service is \
not responding on: NODE, 08001, org.postgresql.util.PSQLException: Connection to \
NODE:5004 refused. Check that the hostname and port are correct and that the \
postmaster is accepting TCP/IP connection.
in the log message field. Which was more than the event description told you. So \
please have patience, but it was really necessary.
However... it looks like issue 7676 [3] should get more attention to solve your \
issue. I claim you are not the only affected user and I hope somebody has an idea for \
a workaround.
PS: I guess using the Rest API [4] to search for alarms is not an option for you. But \
it all I can think of...
Greetings
Marcel
[1] https://issues.opennms.org/browse/HZN-1054
[2] https://issues.opennms.org/browse/NMS-9211
[3] https://issues.opennms.org/browse/NMS-7676
[4] https://docs.opennms.org/opennms/releases/20.0.1/guide-development/guide-development.html#_alarms
"Hernandez, Paul" <Paul_Hernandez@mentor.com<mailto:Paul_Hernandez@mentor.com>> hat \
am 10. August 2017 um 19:48 geschrieben:
Hello,
Just discovered a serious usage impact for us in 20.0.1 versus 19.1.0 with regard to \
the text displayed in the "Log Msg" field on alarms.
In "Advanced Alarm Search", it is critical to be able to use the "Alarm Text \
Contains:" feature to match "reason code" keywords (returned by the SNMP scripts) to \
filter alarms:
[cid:image001.png@01D311D1.F80E7350]
In our current 19.1.0 we see the "reason code" string in Log Message, where it is \
searchable via Alarm Text Contains above:
[cid:image002.png@01D311D1.F80E7350]
But in 20.0.1 we see the "reason code" string has been moved to the Description filed \
which is NOT searchable by any Advanced Search field:
[cid:image003.png@01D311D1.F80E7350]
Service snippet:
<service name="staleNFS" interval="300000" user-defined="false" status="on">
<parameter key="retry" value="1"/>
<parameter key="timeout" value="90000"/>
<parameter key="port" value="161"/>
<parameter key="oid" \
value=".1.3.6.1.4.1.8072.1.3.2.3.1.2.8.115.116.97.108.101.78.70.83" />
<parameter key="operator" value="~"/>
<parameter key="operand" value="^$"/>
<parameter key="reason-template" value="${observedValue}"/>
</service>
So by 20.0.1 moving the "reason code" string from the "Log Message" to the \
"Description" field, the Advanced Search is now no longer able to search the "reason \
code" string.
And there does not exist a field in the Advanced Search form allowing you to search \
the "Description" field.
Any ideas?? Without being able to search the output string of our services scripts it \
becomes impossible to filter only actionable alarms in our env.
Regards,
Paul
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! \
http://sdm.link/slashdot_______________________________________________ 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)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.ox-fb4874f0f6-msonormal, li.ox-fb4874f0f6-msonormal, div.ox-fb4874f0f6-msonormal
{mso-style-name:ox-fb4874f0f6-msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Tahoma",sans-serif;
color:black;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Hi \
Marcel,<o:p></o:p></span></b></p> <p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Well \
that is too bad, as we apparently threw the proverbial baby out with the bathwater \
for the sake of aesthetics.<o:p></o:p></span></b></p> <p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">I do \
appreciate though that it is really hard to be aware of all the inter-dependencies in \
a tool this large.<o:p></o:p></span></b></p> <p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Let's \
hope NMS-7676 happens soon then.<o:p></o:p></span></b></p> <p \
class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Regards,<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Paul<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></b></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span \
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Marcel Fuhrmann \
[mailto:mfuhrmann@mailbox.org] <br>
<b>Sent:</b> Thursday, August 10, 2017 11:31 AM<br>
<b>To:</b> General OpenNMS Discussion \
<opennms-discuss@lists.sourceforge.net><br> <b>Subject:</b> Re: \
[opennms-discuss] "reason code" text now absent in "Log Msg" \
field in 20.0.1 breaks Advanced Search<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hey Paul,<br>
<br>
that sounds really ugly and I don't have a usable workaround.<o:p></o:p></p>
<p>To be honest... I initialized this change [1][2]... because it wasn't correct \
to have detailed information in the alarm title.<o:p></o:p></p> <p>In some cases you \
got messages like this:<o:p></o:p></p> <p>Postgres outage identified on interface \
10.10.7.48 with reason code: JDBC service is not responding on: NODE, 08001, \
org.postgresql.util.PSQLException: Connection to NODE:5004 refused. Check that the \
hostname and port are correct and that the postmaster is accepting TCP/IP \
connection.<o:p></o:p></p> <p>in the log message field. Which was more than the \
event description told you. So please have patience, but it was really \
necessary.<o:p></o:p></p> <p>However... it looks like issue 7676 [3] should get more \
attention to solve your issue. I claim you are not the only affected user and I hope \
somebody has an idea for a workaround.<o:p></o:p></p> <p><o:p> </o:p></p>
<p>PS: I guess using the Rest API [4] to search for alarms is not an option for you. \
But it all I can think of... <o:p></o:p></p> <p><o:p> </o:p></p>
<p>Greetings<o:p></o:p></p>
<p>Marcel<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>[1] <a href="https://issues.opennms.org/browse/HZN-1054">https://issues.opennms.org/browse/HZN-1054<br>
</a>[2] <a href="https://issues.opennms.org/browse/NMS-9211">https://issues.opennms.org/browse/NMS-9211<br>
</a>[3] <a href="https://issues.opennms.org/browse/NMS-7676">https://issues.opennms.org/browse/NMS-7676</a> <br>
[4] <a href="https://docs.opennms.org/opennms/releases/20.0.1/guide-development/ \
guide-development.html#_alarms">https://docs.opennms.org/opennms/releases/20.0.1/guide-development/guide-development.html#_alarms</a><o:p></o:p></p>
<p><o:p> </o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">"Hernandez, Paul" <<a \
href="mailto:Paul_Hernandez@mentor.com">Paul_Hernandez@mentor.com</a>> hat am 10. \
August 2017 um 19:48 geschrieben:<o:p></o:p></p> <div>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Hello,</span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Just discovered a \
<span style="color:black">serious usage impact</span> for us in 20.0.1 versus 19.1.0 \
with regard to the text displayed in the "Log Msg" field on \
alarms.</span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">In "Advanced Alarm \
Search", it is critical to be able to use the "Alarm Text Contains:" feature to match \
"reason code" keywords (returned by the SNMP scripts) to filter \
alarms:</span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><img border="0" width="866" height="332" \
id="ox-fb4874f0f6-Picture_x0020_4" \
src="cid:image001.png@01D311D1.F80E7350"><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><u><span \
style="font-size:14.0pt;font-family:"Tahoma",sans-serif">In our current \
19.1.0<span style="color:black"> we see the "reason code" string in Log Message, \
where it is searchable via Alarm Text Contains \
above:</span></span></u></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><img border="0" width="1394" height="450" \
id="ox-fb4874f0f6-Picture_x0020_2" \
src="cid:image002.png@01D311D1.F80E7350"><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><u><span \
style="font-size:14.0pt;font-family:"Tahoma",sans-serif">But in 20.0.1<span \
style="color:black"> we see the "reason code" string has been moved to the \
Description filed which is NOT searchable by any Advanced Search \
field</span>:</span></u></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><img border="0" width="1413" height="531" \
id="ox-fb4874f0f6-Picture_x0020_3" \
src="cid:image003.png@01D311D1.F80E7350"><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Service \
snippet:</span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <service name="staleNFS" \
interval="300000" user-defined="false" \
status="on"></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <parameter \
key="retry" value="1"/></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <parameter \
key="timeout" value="90000"/></span></strong><o:p></o:p></p> \
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <parameter \
key="port" value="161"/></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <parameter \
key="oid" value=".1.3.6.1.4.1.8072.1.3.2.3.1.2.8.115.116.97.108.101.78.70.83" \
/></span></strong><o:p></o:p></p> <p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <parameter \
key="operator" value="~"/></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <parameter \
key="operand" value="^$"/></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> <span \
style="background:lime"><parameter key="reason-template" \
value="${observedValue}"/></span></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> \
</service></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">So by <span \
style="color:black">20.0.1 </span>moving the "reason code" string from the "Log \
Message" to the "Description" field, the Advanced Search is now \
</span></strong><em><b><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">no longer able to \
search the "reason code" string</span></b></em><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">.</span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">And there does not \
exist a field in the Advanced Search form allowing you to search the "Description" \
field.</span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Any ideas??<span \
style="color:black"> Without being able to search the output string of our services \
scripts it becomes impossible to filter only actionable alarms in our \
env.</span></span></strong><o:p></o:p></p> <p \
class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Regards,</span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Paul</span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:black"> </span></strong><o:p></o:p></p>
<p class="ox-fb4874f0f6-msonormal"><strong><span \
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></strong><o:p></o:p></p>
</div>
</blockquote>
<p><br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">------------------------------------------------------------------------------<br>
Check out the vibrant tech community on one of the world's most<br>
engaging tech sites, Slashdot.org! <a \
href="http://sdm.link/slashdot_______________________________________________"> \
http://sdm.link/slashdot_______________________________________________</a><br> \
Please read the OpenNMS Mailing List FAQ:<br> <a \
href="http://www.opennms.org/index.php/Mailing_List_FAQ">http://www.opennms.org/index.php/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">https://lists.sourceforge.net/lists/listinfo/opennms-discuss</a><o:p></o:p></p>
</blockquote>
</div>
</body>
</html>
["image001.png" (image/png)]
["image002.png" (image/png)]
["image003.png" (image/png)]
[Attachment #9 (--===============7050329117464531112==)]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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