-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Meridian-2017.1.0
-
Fix Version/s: Meridian-2017.1.0
-
Component/s: Thresholding
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Sprint:Horizon - September 20th
We use a different threshold file by default for thresholds in Meridian, demonstrating being able to use thresholds at different levels, like:
<group name="TH-Storage-High-95" rrdRepository="/opt/opennms/share/rrd/snmp/">
<threshold
description="Basic disk threshold for disk drives filled up over 90 percent"
type="high" ds-type="dskIndex" value="95.0" rearm="80.0"
trigger="2" ds-label="ns-dskPath" filterOperator="or" ds-name="ns-dskPercent"/>
<expression
description="Basic disk threshold for disk drives filled up over 90 percent"
type="high" ds-type="hrStorageIndex" value="95.0"
rearm="80.0" trigger="2" ds-label="hrStorageDescr"
triggeredUEI="uei.opennms.org/threshold/highThresholdExceeded"
rearmedUEI="uei.opennms.org/threshold/highThresholdRearmed"
filterOperator="or" expression="hrStorageUsed / hrStorageSize * 100.0">
<resource-filter field="hrStorageType">^\.1\.3\.6\.1\.2\.1\.25\.2\.1\.4$</resource-filter>
</expression>
</group>
Looks like the current thresholds file in Meridian 2017 is from Horizon.
