Log identifiers
Every log entry carries a four-digit numeric identifier alongside its severity. Identifiers are stable across releases — a monitoring rule keyed on 4002 keeps working even if the surrounding message text changes — and are grouped by the kind of event they signal.
| Range | Severity | Domain |
|---|---|---|
| 1000–1999 | debug | Development diagnostics — spawn / dispose, internal state transitions, debug counters. |
| 2000–2999 | info | System lifecycle and normal operation — startup, device-state changes, ingest start, target connect, project load. |
| 3000–3499 | warning | Recoverable issues — missing optional parameter, transient device problem, licence about to expire. |
| 3500–3999 | error | Operation-specific failures — decoder/encoder errors, file access denied, network unreachable, licence-key invalid. |
| 4000–4999 | fatal | Cannot continue — CUDA init failure (4000–4002), codec encoder init failure, audio driver missing, licence verification rejected (4007–4008). |
Use the identifier (not the message text) when writing OpsGenie / Grafana / SIEM rules — message strings are translated and tweaked between releases; identifiers are not.