API · v1 · stabil
CODEMETA OSDeveloper Center
Konsole öffnen
Entity · rmm_alerts

RMM Alert

Schema-ID
rmm_alert
Collection
rmm_alerts
Permissions
  • Lesenrmm_alert_view
  • Anlegenrmm_alert_create
  • Ändernrmm_alert_edit
  • Löschenrmm_alert_delete
Beziehungen

Felder

RMM Alert

rmm_alerts4 Permissions

RMM check-event log entry (ADR 0186 / 0244).

providerstringoptional

Which RMM produced this alert. Absent on pre-0244 docs → octoja.

octojaninjaoneriverbird
Default: "octoja"read-only
externalEventIdstringoptional

Provider-generic event id (idempotency anchor). Fallback: ?? octojaEventId.

read-onlynullable
externalCheckIdstringoptional

Provider-generic check id. Fallback: ?? octojaCheckConfigId.

read-onlynullable
externalDeviceIdstringoptional

Provider-generic device id. Fallback: ?? octojaAssetId.

read-onlynullable
canonicalSeveritystringoptional

Provider-agnostic severity (mapped via RmmProvider.severityMap).

infowarningerrorcritical
read-onlynullable
octojaEventIdstringoptional

Legacy Octoja delivery/event id (deprecated; fallback for externalEventId).

read-onlynullable
octojaCheckAssignmentIdstringoptional
read-onlynullable
octojaCheckConfigIdstringoptional
read-onlynullable
octojaAssetIdstringoptional
read-only
rmmDeviceIduuidoptional
read-onlynullable
partyIduuidoptional
read-onlynullable
deviceNamestringoptional

Denormalised device label for the alert inbox (alias or name).

read-onlynullable
checkNamestringerforderlich
read-only
severitystringerforderlich
WarningCriticalFailure
read-only
statusstringerforderlich
activerecovered
Default: "active"read-only
occurredAtdatetimeoptional
read-onlynullable
recoveredAtdatetimeoptional
read-onlynullable
ticketIduuidoptional→ ticket
read-onlynullable
dedupKeystringerforderlich

Joins recurrences of one check to a single ticket. Octoja (legacy): {tenantId}:{octojaAssetId}:{checkConfigId}. Other providers (ADR 0244): {tenantId}:{provider}:{externalDeviceId}:{externalCheckId}.

read-only
rawOutputobjectoptional
read-onlynullable

Standard-Endpoints

Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:

  • GET /api/v1/rmm_alerts — Liste, paginiert + filterbar
  • GET /api/v1/rmm_alerts/<id> — Einzelne Entity
  • POST /api/v1/rmm_alerts — Anlegen
  • PATCH /api/v1/rmm_alerts/<id> — Teil-Update
  • DELETE /api/v1/rmm_alerts/<id> — Soft-Delete
  • GET /api/v1/rmm_alerts/<id>/timeline — Audit + Aktivitäten

Suche