STANDARD: Messages & alarm messages
InfluxDB background information
See STANDARD: Metrics data collection for more information about how the InfluxDB is constructed, retention policies, measurements, tags and fields.
Alarm messages
Alarms and alarm messages must be sent to the measurement "messages", within the "autogen" retention policy. It is best practice to only log when an alarm occurs, but also when it is cleared.
Tags
Tags must always be strings (see also our MQTT documentation). An alarm message has the following tags:
Tag | Possible values | Meaning |
---|---|---|
nodeId | Any string | Use nodeId for identification. See also the metadata standard. |
msgType | alarm | Indicates what kind of message this is. For now, the message can be an "alarm". Future expansion is possible. |
alarmSeverity | debug undefined | Messages with msgType alarm have a severity assigned to them. undefined: Severity is not (yet) defined. |
alarmType | See separate list | The type of alarm. E.g. "overvoltageAlarm" for an overvoltage. |
Fields
An alarm message must have the following fields:
Tag | Possible values | Meaning |
---|---|---|
alarmActive | True False | Indicates if an alarm is currently active or not. |
msg | Any string | For displaying a predefined message to the end user in Eniris Insights. |
endTime | Timestamp | When the alarm was no longer active. Optional field. |
Example
Example of how an alarm message is stored in the database:
Standardized alarm types
Alarm type | Meaning |
---|---|
overfrequency | |
overvoltageL1 overvoltageL2 overvoltageL3 | |
underfrequency | |
undervoltageL1 undervoltageL2 undervoltageL3 |