We have a EVS Neuron device which is reporting a false-positive alarm.
It report the a Mojor Low alarm on SFP temperature: -1 deg C.
We use a alarm range range and -1 is ofcourse a Major low, however this is not a valid value so I would like to have it as an info severity.
Adding -1 in the info is not working, whcik is logical.
But I'm not able to "hide" this -1 deg C alarm. (withlout using masking)
Any ideas?
Hi John,
I think in this case the best approach is to update the connector. In this case the connector should assign an exception value when receiving '-1'. More information about exception can be found in DataMiner Docs.
Once the exception is available in the connector, in the alarm template you can assign a specific severity to this exception (including the severity 'Info'). In the example below we have a parameter that implements the exception 'No alternate'. This can be selected from a checkbox:
If you would like to avoid assigning alarms to rows that contains this value, you could use conditional monitoring:
Hope it helps!
Hi John,
If this is the method this device uses to indicate an error or exception on the temperature probe, it's probably best to adjust the connector and treat this as an exception value.
You can find more information on the usage of the exception tag here: https://docs.dataminer.services/develop/schemadoc/Protocol/Protocol.Params.Param.Interprete.Exceptions.html