auvik-alerts

# Auvik Alerts Auvik alerts are condition-based notifications generated when a monitored entity (device, interface, network, service) crosses a threshold or changes state. This skill covers the severity model, the status lifecycle, and the dismissal semantics that confuse new users. ## Tools | Tool | Use For | |------|---------| | `auvik_alerts_list` | List alerts, filterable by status / severity / tenant | | `auvik_alerts_get` | Full record for one alert | | `auvik_alerts_dismiss` | Acknowledge and hide an alert | ## Severity Severity values, in increasing order: | Severity | Meaning | |----------|---------| | `info` | Informational - state change, no impact | | `warning` | Worth attention but not service-affecting | | `critical` | Service affecting; respond now | | `emergency` | Highest tier; usually a managed infrastructure device down | Default triage filter is `severity >= warning` - `info` alerts drown the queue and are rarely actionable. ## Status | Status | Meaning | |--------|---------| | `open` | Currently active | | `dismissed` | Acknowledged by a user; hidden from the default UI view | | `closed` | Condition cleared on its own | `closed` is the only "the problem is fixed" state. `dismissed` is "a human decided not to look at this" - the underlying condition may or may not still hold. ## Dismissal Semantics **Dismissing an alert does not fix the underlying condition.** Auvik's alert engine evaluates conditions on a recurring schedule. If you dismiss an...