Alarms Count

Use this node to count alarms matching configured criteria and write the count as telemetry — for example, maintaining a real-time activeAlarmCount metric on a device asset that increments when new alarms are created and decrements when they are cleared, or tracking how many critical alarms occurred in the last 24 hours.

• Count alarms for propagation entities — when enabled, counts alarms not only for the message originator but also for all entities to which those alarms are propagated.

A table where each row defines one alarm count metric:

1. Receive an alarm-related message: ALARM, ALARM_ACK, ALARM_CLEAR, or ENTITY_CREATED / ENTITY_UPDATED about an alarm.
2. For each mapping row, execute an alarm count query against the originator entity (and propagated entities if configured), applying the status, severity, type, and time interval filters.
3. Write each count result as a POST_TELEMETRY_REQUEST message with the originator as the entity.
4. Route generated messages via Success. If the count query fails for an entity, route a failure message via Failure.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "TbAlarmsCountNodeConfiguration",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "countAlarmsForPropagationEntities": { "type": "boolean" },
    "alarmCountMappings": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "targetKey": { "type": "string" },
          "statusList": { "type": "array", "items": { "type": "string" } },
          "severityList": { "type": "array", "items": { "type": "string" } },
          "typeList": { "type": "array", "items": { "type": "string" } },
          "specifyInterval": { "type": "boolean" }
        }
      }
    }
  }
}