The event_alarms node-map parser only reads severity_override:. A severity: key on an event_alarms entry is silently ignored (no unknown-key validation), so the configured severity never reaches the fault.
This is inconsistent with the threshold alarm: block, which uses severity:. An operator who reuses severity: for an event alarm gets the wrong severity: the value is dropped and the fault falls back to the live OPC UA event Severity. For sources whose events carry a low default Severity, an important alarm then surfaces as INFO.
Proposal
- In the
event_alarms loader, accept severity: as an alias for severity_override: (source-level and per-mapping), validated like the threshold path.
- Warn on unknown keys in the
event_alarms block so future typos are not silently dropped.
- Keep the existing precedence: an explicit configured severity wins over the live event Severity; with none configured, the event Severity band mapping applies.
Acceptance
An event_alarms entry configured with severity: ERROR (no severity_override:) raises the fault at ERROR regardless of the live event Severity.
The
event_alarmsnode-map parser only readsseverity_override:. Aseverity:key on anevent_alarmsentry is silently ignored (no unknown-key validation), so the configured severity never reaches the fault.This is inconsistent with the threshold
alarm:block, which usesseverity:. An operator who reusesseverity:for an event alarm gets the wrong severity: the value is dropped and the fault falls back to the live OPC UA event Severity. For sources whose events carry a low default Severity, an important alarm then surfaces as INFO.Proposal
event_alarmsloader, acceptseverity:as an alias forseverity_override:(source-level and per-mapping), validated like the threshold path.event_alarmsblock so future typos are not silently dropped.Acceptance
An
event_alarmsentry configured withseverity: ERROR(noseverity_override:) raises the fault at ERROR regardless of the live event Severity.