[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-buglist
Subject:    [Buglist] [Bug 3447] New: SnmpMonitor with match-all=count broken
From:       bugzilla () opennms ! org (bugzilla at opennms ! org)
Date:       2009-11-20 13:25:32
Message-ID: bug-3447-627 () http ! bugzilla ! opennms ! org/
[Download RAW message or body]

http://bugzilla.opennms.org/show_bug.cgi?id=3447

           Summary: SnmpMonitor with match-all=count broken
           Product: OpenNMS
           Version: 1.7.7
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: Poller
        AssignedTo: buglist at opennms.org
        ReportedBy: dk at in-telegence.net


capsd:
    <protocol-plugin protocol="ProcessZshCount"
class-name="org.opennms.netmgt.capsd.plugins.SnmpPlugin" scan="on"
user-defined="false">
        <property key="timeout" value="2000"/>
        <property key="retry" value="2"/>
        <property key="vbname" value=".1.3.6.1.2.1.25.4.2.1.2.1"/>
    </protocol-plugin>

poller:
    <service name="ProcessZshCount" interval="30000" user-defined="false"
status="on">
      <parameter key="walk" value="true"/>
      <parameter key="retry" value="2"/>
      <parameter key="timeout" value="3000"/>
      <parameter key="port" value="161"/>
      <parameter key="match-all" value="count"/>
      <parameter key="oid" value=".1.3.6.1.2.1.25.4.2.1.2"/>
      <parameter key="operator" value="~"/>
      <parameter key="operand" value="^zsh$"/>
      <parameter key="minimum" value="3" />
      <parameter key="maximum" value="10" />
      <parameter key="reason-template" value="observedValue ${observedValue}
matchCount ${matchCount} minimum ${minimum} maximum ${maximum} matchAll
${matchAll} walk ${walk}" />
    </service>
...
  <monitor service="ProcessZshCount"
class-name="org.opennms.netmgt.poller.monitors.SnmpMonitor" />

When 0 zsh processes run on the Node, the service is considered "down". As soon
as 1 zsh process is running, the service is considered "up". This should only
start at the configured minimum. If 11 zsh processes are running, the service
is still considered up. This should be considered "down", since the configured
maximum is 10.

And apart from that, the reason-template is not visible in the webUI. Instead I
can only see "reason code unknown".

Please let me know if you need more information or logs or whatever. I am
usually on irc during european business hours for quicker response.


-- 
Configure bugmail: http://bugzilla.opennms.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[prev in list] [next in list] [prev in thread] [next in thread]