Opennms Threshold
- Category: 電腦相關
- Last Updated: Tuesday, 20 December 2016 23:33
- Published: Wednesday, 05 October 2016 09:34
- Written by sam
在使用OpenNMS時
預設在serviceDown, sericeUP, nodeDown, nodeUp時
會自動的清除相關Alarm,也就是在Dashboard的顯示會自動消失
但在使用了lowthreshold, highthreshold時,卻不會如此
必需要手動的去作Acknowledged
以下是修改好的檔案
直接取代這四段event的值即可
/etc/opennms/events# vi opennms.events.xml
<event> <uei>uei.opennms.org/threshold/highThresholdExceeded</uei> <event-label>OpenNMS-defined threshold event: highThresholdExceeded</event-label> <descr><p>High threshold exceeded for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%</p> <p>By default, OpenNMS watches some key parameters on devices in your network and will alert you with an event if certain conditions arise. For example, if the CPU utilization on your Cisco router maintains an inordinately high percentage of utilization for an extended period, an event will be generated. These thresholds are determined and configured based on vendor recommendations, tempered with real-world experience in working deployments.</p> <p>This specific event indicates that a high threshold was exceeded.</p></descr> <logmsg dest="logndisplay">High threshold exceeded for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%</logmsg> <severity>Warning</severity> <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[trigger]%:%parm[rearm]%" alarm-type="1" auto-clean="false"/> </event> <event> <uei>uei.opennms.org/threshold/lowThresholdExceeded</uei> <event-label>OpenNMS-defined threshold event: lowThresholdExceeded</event-label> <descr><p>Low threshold exceeded for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%.</p> <p>By default, OpenNMS watches some key parameters on devices in your network and will alert you with an event if certain conditions arise. For example, if the CPU utilization on your Cisco router maintains an inordinately high percentage of utilization for an extended period, an event will be generated. These thresholds are determined and configured based on working experience with real deployments, not vendor recommendation alone.</p> <p>This specific event indicates that a low threshold was exceeded.</p></descr> <logmsg dest="logndisplay">Low threshold exceeded for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%</logmsg> <severity>Warning</severity> <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[trigger]%:%parm[rearm]%" alarm-type="1" auto-clean="false"/> </event> <event> <uei>uei.opennms.org/threshold/highThresholdRearmed</uei> <event-label>OpenNMS-defined threshold event: highThresholdRearmed</event-label> <descr><p>High threshold has been rearmed for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%</p> <p>By default, OpenNMS watches some key parameters on devices in your network and will alert you with an event if certain conditions arise. For example, if the CPU utilization on your Cisco router maintains an inordinately high percentage of utilization for an extended period, an event will be generated. These thresholds are determined and configured based on vendor recommendations, tempered with real-world experience in working deployments.</p> <p>This specific event indicates that a high threshold was exceeded but then dropped below the rearm threshold..</p></descr> <logmsg dest="logndisplay">High threshold rearmed for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%</logmsg> <severity>Normal</severity> <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[trigger]%:%parm[rearm]%" alarm-type="2" clear-key="uei.opennms.org/threshold/highThresholdExceeded:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[trigger]%:%parm[rearm]%" auto-clean="false"/> </event> <event> <uei>uei.opennms.org/threshold/lowThresholdRearmed</uei> <event-label>OpenNMS-defined threshold event: lowThresholdRearmed</event-label> <descr><p>Low threshold has been rearmed for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%.</p> <p>By default, OpenNMS watches some key parameters on devices in your network and will alert you with an event if certain conditions arise. For example, if the CPU utilization on your Cisco router maintains an inordinately high percentage of utilization for an extended period, an event will be generated. These thresholds are determined and configured based on working experience with real deployments, not vendor recommendation alone.</p> <p>This specific event indicates that a low threshold was exceeded but then dropped below the rearm threshold.</p></descr> <logmsg dest="logndisplay">Low threshold rearmed for %service% datasource %parm[ds]% on interface %interface%, parms: %parm[all]%</logmsg> <severity>Normal</severity> <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[trigger]%:%parm[rearm]%" alarm-type="2" clear-key="uei.opennms.org/threshold/lowThresholdExceeded:%dpname%:%nodeid%:%interface%:%parm[ds]%:%parm[trigger]%:%parm[rearm]%" auto-clean="false"/> </event>