Einführung
Sehen Sie jede Warnung that's fired on a device, dig into what triggered it, and track how it was resolved. The Warnungen tab in device details scopes the global alerts view down to a single device — same data, tighter context.
Aktive Warnungen
The Aktiv tab lists every open alert for the device. Each row shows the alert's severity badge, what triggered it, when it started, and whether an automation ran in response.
Warnungstabelle
Jede Warnungszeile enthält:
Schweregrad — the alert level set on the monitor: Information, Warnung, Kritisch oder Neintfall
Trigger-Details — der Monitor-Name und die ausgelöste Bedingung (e.g., "CPU usage >75.0% for 10 minutes")
Warnung gestartet — when the alert first opened
Automatisierung ausgeführt — wenn eine Behebungsautomatisierung verknüpft wurde to the monitor, its name appears here; click it to view that automation run's details
💡 TIPP: If an automation ran, open it from this column to see exactly what actions executed, what the output was, and whether remediation succeeded — without leaving the device context.
Warnungs-Payload
Klicken Sie auf die › chevron on any row to expand the alert payload. What you see depends on the monitor type:
CPU-Monitore show the top processes by CPU usage at the time the alert triggered
Speicher-Monitore show the top processes by memory consumption
Skript-Monitore show the raw output your script returned
Ereignisprotokoll-Monitore show the matching event details, including Event ID, source, and message
The payload is captured when the alert opens and stays static as long as the alert remains open. If you resolve the alert and it later reopens, the payload updates to reflect conditions at the time it reopened.
Suchen und Filternn
Use the Suchen field to filter alerts by monitor name or trigger text. Klicken Sie auf Filtern zum Filternn nach Schweregrad. Klicken Sie auf Spalten to show or hide the Warnungsquelle column (hidden by default), which identifies which monitor policy the alert originated from.
Behebung von Warnungen
💡 TIPP: If the monitor has Automatische Behebung enabled, Level closes the alert automatically once the condition clears. You don't need to manually resolve it.
To resolve a single alert, open its row menu (the ⋮ icon) and select Beheben. To resolve multiple alerts at once, check the boxes next to the rows you want, then click Beheben in the toolbar.
ℹ️ HINWEIS: Resolving an alert marks it as closed. If the same monitor condition is detected again within 24 hours, Level reopens the existing alert rather than creating a new one — and keeps the original start timestamp. You'll likely see the alert come back to the Aktiv tab instead of appearing under Behoben. After 24 hours without re-triggering, Level creates a fresh alert.
Behobene Warnungen
The Behoben tab shows every alert that's been closed, whether by a technician, an automation, or auto-resolve. Warnungen are stored indefinitely — there's no expiration.
The resolved table adds two columns not present on the Aktiv tab:
Warnung behoben — when the alert was closed
Behoben by — who or what closed it: a technician's name, "Automatische Behebungd" if the monitor's auto-resolve fired, or blank if resolved via automation
The resolved tab also supports search, making it practical for reviewing a specific monitor's history. Expand any resolved alert row to see its payload, just like on the Aktiv tab.
💡 TIPP: Use the resolved tab to audit recurring issues. If the same monitor is firing and resolving repeatedly, that's a signal to investigate the root cause or adjust the monitor threshold.
Häufig gestellte Fragen
Why did an alert disappear from Aktiv but I can't find it under Behoben? Level reopens an existing alert if the same monitor fires again within 24 hours. When it reopens, it goes back to Aktiv — and it keeps the original start time, so the timestamps can look confusing. Check the Aktiv tab and look for an older start date on a current alert.
Who can resolve alerts on a device? Any technician with access to the device's group can resolve alerts. Berechtigungs are configured at the group level. See Workspace → Berechtigungs for details on how access is scoped.
What does the Automatisierung ausgeführt column show if no automation was linked to the monitor? It shows
--. An automation only appears there if the monitor that triggered the alert had a remediation automation configured.The alert payload is blank — why? Some monitor types don't generate a payload. Connection monitors (offline alerts) and process/service monitors may show no payload beyond the trigger condition itself. Skript-Monitore only populate a payload if your script outputs text to stdout.
Why does an alert show a start time from months ago but still appears in Aktiv? The original start timestamp is preserved every time an alert reopens. If a monitor has been cycling — firing, auto-resolving, and firing again — the start time reflects when the alert first opened, not its most recent trigger.