Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
18.0.3, 21.0.1
-
Security Level: Default (Default Security Scheme)
-
Horizon - April 25th 2018, Horizon - May 2nd 2018
Description
If your threshold config is broken (eg. broken XML code), ONMS starts without problems.
But you will get no alarms. Collectd log then says:
2017-01-31 13:39:57,271 ERROR [Collectd-Thread-1-of-50] o.o.n.t.ThresholdingSet: initThresholdsDao: Could not initialize DefaultThresholdsD
ao
org.exolab.castor.xml.MarshalException: The element type "group" must be terminated by the matching end-tag "</group>".
An ONMS start should validate the threshold xml code while starting. Like other problems this error messages should appear in output.log.
Attachments
Issue Links
- has to be finished together with
-
NMS-9811 Thresholds should work without restart when putting nodes into categories
-
- Resolved
-
-
NMS-9736 Thresholding not working on HTTP data collections
-
- Open
-
-
NMS-9790 While doing threshold configuration, then not able to get all property values from string.properties file
-
- Open
-
-
NMS-9612 If thresholds config parts are missing, collectd doesn't collect SNMP data
-
- Resolved
-
-
NMS-9759 Threshold expression can't handle metric names with leading zero
-
- Closed
-
- is duplicated by
-
NMS-9612 If thresholds config parts are missing, collectd doesn't collect SNMP data
-
- Resolved
-