Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.2.8
-
Component/s: Thresholding
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:Operating System: Linux
Platform: PC
URL: http://sourceforge.net/mailarchive/forum.php?thread_id=30459123&forum_id=40670
-
Bugzilla Id:1582
Description
As I know when the settings for threshold are:
<group name="icmp-latency"
rrdRepository = "/var/lib/opennms/rrd/response/">
<threshold type="high" ds-name="icmp" ds-type="if"
value="75000" rearm="25000" trigger="5"/>
</group>
OpenNMS should send alert when ping exceeds value 75000 five polls in a
row. But here is an example when OpenNMS sends alert on second poll when
threshold exceeded:
threshd.log:
1st poll:
2006-09-04 07:01:52,717 DEBUG [ThreshdScheduler-5 Pool-fiber4]
LatencyThresholder: check: service= ICMP interface= 172.16.254.29
nodeId= 44 thresholding-group=icmp-latency interval=300000ms
2006-09-04 07:01:52,717 DEBUG [ThreshdScheduler-5 Pool-fiber4]
LatencyThresholder: check: rrd repository=/var/lib/opennms/rrd/response/
2006-09-04 07:01:52,717 DEBUG [ThreshdScheduler-5 Pool-fiber4]
LatencyThresholder: checkPerformanceDir: threshold checking dir:
/var/lib/opennms/rrd/response/172.16.254.29
2006-09-04 07:01:52,717 DEBUG [ThreshdScheduler-5 Pool-fiber4]
LatencyThresholder: checking value of last possible PDP only
2006-09-04 07:01:52,717 DEBUG [ThreshdScheduler-5 Pool-fiber4]
JniRrdStrategy: fetch: Issuing RRD command: fetch
/var/lib/opennms/rrd/response/172.16.254.29/icmp.rrd AVERAGE -s now-300
-e now-300
2006-09-04 07:01:52,772 DEBUG [ThreshdScheduler-5 Pool-fiber4]
JniRrdStrategy: fetch: fetch successful: icmp= 1698.8533333
2006-09-04 07:01:52,772 DEBUG [ThreshdScheduler-5 Pool-fiber4]
ThresholdEntity: evaluate: value= 1698.8533333 against threshold:
dsName=icmp,dsType=if: highVal=75000.0,highRearm=25000.0,highTrigger=5
2006-09-04 07:01:52,773 DEBUG [ThreshdScheduler-5 Pool-fiber4]
Scheduler: schedule: Adding ready runnable
org.opennms.netmgt.threshd.ThresholdableService@18a9fc8 at interval
300000
2006-09-04 07:01:52,773 DEBUG [ThreshdScheduler-5 Pool-fiber4]
Scheduler: schedule: queue element added, notification not performed
2nd poll:
2006-09-04 07:06:53,463 DEBUG [ThreshdScheduler-5 Pool-fiber4]
JniRrdStrategy: fetch: Issuing RRD command: fetch
/var/lib/opennms/rrd/response/172.16.254.29/icmp.rrd AVERAGE -s now-300
-e now-300
2006-09-04 07:06:53,463 DEBUG [ThreshdScheduler-5 Pool-fiber4]
JniRrdStrategy: fetch: fetch successful: icmp= 315766.18
2006-09-04 07:06:53,463 DEBUG [ThreshdScheduler-5 Pool-fiber4]
ThresholdEntity: evaluate: value= 315766.18 against threshold:
dsName=icmp,dsType=if: highVal=75000.0,highRearm=25000.0,highTrigger=5
2006-09-04 07:06:53,463 DEBUG [ThreshdScheduler-5 Pool-fiber4]
ThresholdEntity: evaluate: high threshold exceeded, count=4
2006-09-04 07:06:53,463 DEBUG [ThreshdScheduler-5 Pool-fiber4]
Scheduler: schedule: Adding ready runnable
org.opennms.netmgt.threshd.ThresholdableService@18a9fc8 at interval
300000
2006-09-04 07:06:53,464 DEBUG [ThreshdScheduler-5 Pool-fiber4]
Scheduler: schedule: queue element added, notification not performed
3rd poll:
2006-09-04 07:11:54,293 DEBUG [ThreshdScheduler-5 Pool-fiber4]
JniRrdStrategy: fetch: Issuing RRD command: fetch
/var/lib/opennms/rrd/response/172.16.254.29/icmp.rrd AVERAGE -s now-300
-e now-300
2006-09-04 07:11:54,294 DEBUG [ThreshdScheduler-5 Pool-fiber4]
JniRrdStrategy: fetch: fetch successful: icmp= 81693.406667
2006-09-04 07:11:54,294 DEBUG [ThreshdScheduler-5 Pool-fiber4]
ThresholdEntity: evaluate: value= 81693.406667 against threshold:
dsName=icmp,dsType=if: highVal=75000.0,highRearm=25000.0,highTrigger=5
2006-09-04 07:11:54,294 DEBUG [ThreshdScheduler-5 Pool-fiber4]
ThresholdEntity: evaluate: high threshold exceeded, count=5
2006-09-04 07:11:54,294 DEBUG [ThreshdScheduler-5 Pool-fiber4]
ThresholdEntity: evaluate: high threshold triggered!
rrd.xml:
<!-- 2006-09-04 06:30:00 CEST / 1157344200 --> <row><v>
2.0627266667e+03 </v></row>
<!-- 2006-09-04 06:35:00 CEST / 1157344500 -->
<row><v> 1.7620166667e+03 </v></row>
<!-- 2006-09-04 06:40:00 CEST / 1157344800 -->
<row><v> 1.7191200000e+03 </v></row>
<!-- 2006-09-04 06:45:00 CEST / 1157345100 -->
<row><v> 2.3050833333e+03 </v></row>
<!-- 2006-09-04 06:50:00 CEST / 1157345400 -->
<row><v> 1.9532533333e+03 </v></row>
<!-- 2006-09-04 06:55:00 CEST / 1157345700 -->
<row><v> 1.6988533333e+03 </v></row>
<!-- 2006-09-04 07:00:00 CEST / 1157346000 -->
<row><v> 3.1576618000e+05 </v></row>
<!-- 2006-09-04 07:05:00 CEST / 1157346300 -->
<row><v> 8.1693406667e+04 </v></row>
<!-- 2006-09-04 07:10:00 CEST / 1157346600 -->
<row><v> 7.5631266667e+03 </v></row>
<!-- 2006-09-04 07:15:00 CEST / 1157346900 -->
<row><v> 2.8765233333e+03 </v></row>
It seems like OpenNMS doesn't reset the count of exceeded thresholds. And this
occurs consistently.
My config:
OpenNMS Version: 1.2.8-1
Java Version: 1.4.2_12 Sun Microsystems Inc.
Java Virtual Machine: 1.4.2_12-b03 Sun Microsystems Inc.
Operating System: Linux 2.6.8-2-386 (i386)
Servlet Container: Apache Tomcat/4.1 (Servlet Spec 2.3)