Re: Changing the severity of node down events.

Does anyone have any ideas on how to have different severities for different Windows Services being unavailable?

Regards,
John







From: JohnD Blackburn [mailto:[email protected]]
Sent: Thursday, 22 March 2018 12:58 PM
To: General OpenNMS Discussion <[email protected]>
Subject: [opennms-discuss] Changing the severity of node down events.


Hi all,

I've recently set up Windows Service monitoring with the following configuration:


Default-foreign-source.xml:
      <detector name="WIN-Application-Host-Helper-Service" class="org.opennms.netmgt.provision.detector.snmp.Win32ServiceDetector">
         <parameter key="port" value="161"/>
         <parameter key="win32ServiceName" value="Application Host Helper Service"/>
      </detector>
      <detector name="WIN-Connected-Devices-Platform-Service" class="org.opennms.netmgt.provision.detector.snmp.Win32ServiceDetector">
         <parameter key="port" value="161"/>
         <parameter key="win32ServiceName" value="Connected Devices Platform Service"/>
      </detector>
      <detector name="WIN-CoreMessaging" class="org.opennms.netmgt.provision.detector.snmp.Win32ServiceDetector">
         <parameter key="port" value="161"/>
         <parameter key="win32ServiceName" value="CoreMessaging"/>
      </detector>
... (one per service that we want to monitor)


Poller-configuration.xml:
      <service name="WIN-Application-Host-Helper-Service" interval="300000" user-defined="false" status="on">
          <parameter key="retry" value="6"/>
          <parameter key="timeout" value="4950"/>
          <parameter key="port" value="161"/>
          <parameter key="service-name" value="Application Host Helper Service"/>
      </service>
      <service name="WIN-Connected-Devices-Platform-Service" interval="300000" user-defined="false" status="on">
         <parameter key="retry" value="6"/>
         <parameter key="timeout" value="4950"/>
         <parameter key="port" value="161"/>
         <parameter key="service-name" value="Connected Devices Platform Service"/>
      </service>
      <service name="WIN-CoreMessaging" interval="300000" user-defined="false" status="on">
         <parameter key="retry" value="6"/>
         <parameter key="timeout" value="4950"/>
         <parameter key="port" value="161"/>
         <parameter key="service-name" value="CoreMessaging"/>
      </service>
...
   <monitor service="WIN-Application-Host-Helper-Service" class-name="org.opennms.netmgt.poller.monitors.Win32ServiceMonitor"/>
   <monitor service="WIN-Connected-Devices-Platform-Service" class-name="org.opennms.netmgt.poller.monitors.Win32ServiceMonitor"/>
   <monitor service="WIN-CoreMessaging" class-name="org.opennms.netmgt.poller.monitors.Win32ServiceMonitor"/>
... (one per service being monitored)

And this is working well.

But, I have had a request to have different severities raised for different services being down, and was trying to set that up with the following event definition using mask elements:

   <event>
      <mask>
         <maskelement>
            <mename>service</mename>
            <mevalue>WIN-Application-Host-Helper-Service</mevalue>
         </maskelement>
      </mask>
      <uei>uei.opennms.org/nodes/nodeLostService</uei>
      <event-label>OpenNMS-defined node event: nodeLostService</event-label>
      <descr>&lt;p>A %service% outage was identified on interface
            %interface% because of the following condition: %parm[eventReason]%.&lt;/p> &lt;p>
            A new Outage record has been created and service level
            availability calculations will be impacted until this outage is
            resolved.&lt;/p></descr>
      <logmsg dest="logndisplay">
            %service% outage identified on interface %interface%.
        </logmsg>
      <severity>Critical</severity>
      <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%service%" alarm-type="1" auto-clean="false"/>
   </event>

However, I'm finding that this event definition is changing the severity for ALL nodeLostService events, and is not restricted to the specific Windows service.

Is there something wrong with my event definition, or mask element usage? Or is there a better way to achieve the requested objective of different severity for specific Windows service?

Regards,
John

------------------------------------------------------------------------------
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