[opennms-discuss] OpenNMS thresholds and notifications customizations not working

[Paul-Andre P. <Pau...@dh...>]

Hello,

I'm trying to do a few things with custom thresholds and notifications but it doesn't seem to be working. The installed version of OpenNMS is 1.8.10. This site already has a Nagios installation which I'm trying to replace, and therefore has the Nagios client installed on most Windows monitoring targets. It also has a few Netware servers, which are monitored via SNMP.

In addition to the default SNMP-based configuration, I want to add thresholds and notifications based on the Netware disk/cpu usage values, and based on performance counter values returned by the NSClient++ plugin.

What works:

 - email notifications for standard node/service up/down/add events
 - email notifications for standard mib2 expression thresholds (i.e. if*Discards  or if*Octet counts)
 - data collection and graphing of Netware SNMP data including disk usage data
 - custom data collection and graphing of disk/cpu/memory usage data obtained from NSClient++

What doesn't seem to work:
 - email notifications for standard hrstorage threshold events (I see some notification entries in the Notices list off the main page, but haven't received any e-mails for those)
 - I don't get any notifications from my custom NSClientpp thresholds

Here is what I have tried:

The NSClient data collection is mostly set up similar to     http://www.opennms.org/wiki/Data_collection_from_Windows_Performance_Counters_with_NSClient++

However, I have added separate packages and services in the poller-config to filter data collection of drive letters based on include-url lists of IP addresses. Only some IPs are included for additional NSClientpp services that are limited to a particular drive. That helps cut down on errors in the NSClient++ log files. I also have some working snmp-graphs definitions that show the data nicely, so the data collection portion seems to work fine.

I modified the NSCLientpp* service entries in poller-config to enable thresholding according to
   http://www.opennms.org/wiki/Creating_Threshold_Alarms

I created new expression thresholds for the NSClient and Netware datasources (where ldfreespace[c-h] contain %Available Windows perf data for those drives):

    <group name="nsclient" rrdRepository="D:/Program Files/OpenNMS/share/rrd/snmp/">
        <expression type="high" ds-type="node" value="80.1" rearm="80.0"
            trigger="2" expression="100.0 - ldfreespacec"/>
        <expression type="high" ds-type="node" value="80.1" rearm="80.0"
            trigger="2" expression="100.0 - ldfreespaced"/>
        <expression type="high" ds-type="node" value="80.1" rearm="80.0"
            trigger="2" expression="100.0 - ldfreespacee"/>
        <expression type="high" ds-type="node" value="80.1" rearm="80.0"
            trigger="2" expression="100.0 - ldfreespacef"/>
        <expression type="high" ds-type="node" value="80.1" rearm="80.0"
            trigger="2" expression="100.0 - ldfreespaceg"/>
        <expression type="high" ds-type="node" value="80.1" rearm="80.0"
            trigger="2" expression="100.0 - ldfreespaceh"/>
        <threshold type="relativeChange" ds-type="node" value="0.5"
            rearm="0.0" trigger="2" filterOperator="or" ds-name="ldfreespacec"/>
        <threshold type="relativeChange" ds-type="node" value="0.5"
            rearm="0.0" trigger="2" filterOperator="or" ds-name="ldfreespaced"/>
        <threshold type="relativeChange" ds-type="node" value="0.5"
            rearm="0.0" trigger="2" ds-label="" filterOperator="or" ds-name="ldfreespacee"/>
        <threshold type="relativeChange" ds-type="node" value="0.5"
            rearm="0.0" trigger="2" ds-label="" filterOperator="or" ds-name="ldfreespacef"/>
        <threshold type="relativeChange" ds-type="node" value="0.5"
            rearm="0.0" trigger="2" ds-label="" filterOperator="or" ds-name="ldfreespaceg"/>
        <threshold type="relativeChange" ds-type="node" value="0.5"
            rearm="0.0" trigger="2" ds-label="" filterOperator="or" ds-name="ldfreespaceh"/>
        <threshold type="high" ds-type="node" value="95.0" rearm="90.0"
            trigger="2" ds-label="" filterOperator="or" ds-name="cpuProcTime"/>
    </group>
    <group name="netware-snmp" rrdRepository = "D:/Program Files/OpenNMS/share/rrd/snmp/">
        <threshold type="high" ds-type="node" value="95" rearm="75.0"
            trigger="2" ds-name="cpuPercentBusy"/>
        <expression type="high" ds-type="netwareDisk" value="90.0"
            rearm="75.0" trigger="2" ds-label="nwLabel"
            filterOperator="or" expression="(nwVolSize - nwFreeSpace) / nwVolSize * 100.0">
            <resource-filter field="hrStorageType">^\.1\.3\.6\.1\.2\.1\.25\.2\.1\.4$</resource-filter>
        </expression>
        <expression type="relativeChange" ds-type="netwareDisk"
            value="0.5" rearm="0.0" trigger="2"
            ds-label="nwLabel" filterOperator="or" expression="(nwVolSize - nwFreeSpace) / nwVolSize * 100.0">
            <resource-filter field="hrStorageType">^\.1\.3\.6\.1\.2\.1\.25\.2\.1\.4$</resource-filter>
        </expression>
     </group>



I didn't create any special events or notification definitions because I would prefer to use the standard highThresholdExceeded UEIs and associated notifications. I don't see any need for any variation and it would be one more thing to maintain. I would have thought that the above would be sufficient, but I don't see why I don't get the e-mail notifications for the cases outlined earlier in this post (including the standard hrstorage thresholds). And yet the stock config does work with thresholds for the mib2 interface stats.

Any pointers would be appreciated. Thanks,

Paul-Andre Panon
Systems Management
D+H Limited Partnership
200 - 4216 Norland Ave.
Burnaby, BC V5G 3S8
T: (604) 637-4030
C: (778) 995-8437
E: Pau...@dh...


Notice of Confidentiality: This message is private and confidential intended for the addressee only. If you received this message in error, please contact the sender immediately and destroy all copies of this transmission. Any copying, re-transmission, distribution, disclosure or other use of this information including taking or omitting any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.

Avis de confidentialité: Ce message contient des renseignements confidentiels et privés à l'intention du ou des destinataires seulement. Si vous recevez ce message par erreur, veuillez en aviser immédiatement l'expéditeur et détruire toutes les copies de la transmission. Sont interdites toute copie, retransmission, distribution, divulgation ou toute autre utilisation de ces renseignements, y compris les mesures qui seraient prises ou non à cet égard par des personnes ou des entités autres que le ou les destinataires.