Alarm Schema

Lifecycle: OPEN → ACKNOWLEDGED (in Bearbeitung) → RESOLVED (source sent CLEAR) | CLOSED (manual or auto_close action).

Computed: true while status is OPEN or ACKNOWLEDGED. Exists solely for the unique partial index (one open alarm per dedupKey) — always derive from status, never set independently.

Display severity from the FIRST matching rule; fallback: severityHint mapping (critical→error) when no rule matched.

Provider-mapped 4-level severity of the first RAISE (RmmSeverity). Kept alongside the 3-level display severity because ticket-priority policies are 4-level — the seeded default rule maps priorities from THIS field (fixed-policy parity).

Provider-scoped identity (ADR 0244) — passed through, never recomputed.

RMM provider id (octoja|riverbird|…).

integration_config the events came from.

Check name/category ("Fehlerart") — snapshot from the first RAISE.

Normalized check type (RMM_CHECK_TYPES catalog value), null when unknown.

Human-readable check output — updated on UPDATE events.

Normalized device category (RMM_DEVICE_CATEGORIES value).

CMDB asset of the device — snapshot of rmm_device.assetId at alarm creation; null = no match ("ohne Asset" marker in the UI).

Ticket created/attached by a create_ticket action.

All rules that matched (evaluation transparency in the UI).

A rule matched but its exception suppressed all actions.

OR over the matching rules — a pinned alarm cannot be hidden.

Users who hid this alarm from their board (only when not pinned).

Pending BullMQ action jobIds — best-effort cancel bookkeeping on CLEAR/ack.

Idempotency keys of actions that already fired. The authoritative dedup — BullMQ jobId dedup ends at removeOnComplete.