auvik-network-alerts

Surface and triage Auvik network alerts by severity, status, tenant, or time window.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill auvik-network-alerts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auvik-network-alerts
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/auvik-network-alerts
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill auvik-network-alerts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network operations teams using Auvik need a fast way to query and triage alert history across MSP tenants without manually clicking through the Auvik Dashboard, especially during incident reviews and post-mortems.

Core Features & Use Cases

  • Alert Listing and Filtering: Query Auvik alert history filtered by severity (emergency/critical/warning/info), status (created/resolved/paused), dismissed state, entity, tenant, or ISO-8601 time window.
  • Device Name Resolution: Pass a device name, hostname, or IP address and the server resolves it to the Auvik internal entity ID, returning candidates when multiple devices match.
  • MSP Tenant Scoping: Scope queries to a single managed client or aggregate across all visible tenants, with automatic cursor pagination up to a configurable page cap.
  • Use Case: During a morning triage, list all open critical alerts for a specific client, cross-reference the alerting devices against lifecycle data to spot end-of-life hardware, and record findings in a GAIT audit branch.

Quick Start

Ask the agent to list all open critical and emergency Auvik alerts for a specific client tenant from the last 24 hours.

Frequently Asked Questions about auvik-network-alerts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list open Auvik alerts by severity?

Call auvik_list_alerts with status=created to see only open alerts, then add severity=critical or severity=emergency for priority triage. Add dismissed=false to exclude alerts that were silenced in the Dashboard.

How do I check alert history for a specific device in Auvik?

Pass the device name, hostname, or IP address as the entity parameter to auvik_list_alerts and the server resolves it to the Auvik entity ID. If the name matches multiple devices, the tool returns resolution candidates so you can narrow the query.

Can I dismiss or acknowledge Auvik alerts through the API?

No, this skill is read-only and only performs GET operations against the Auvik API. Alert dismissal, acknowledgment, and state changes must be performed directly in the Auvik Dashboard.

How do I pull Auvik alerts for a specific time range?

Use the detected_time_after and detected_time_before parameters with ISO-8601 datetime strings such as 2026-06-01T00:00:00Z to bound the query window. This is useful for incident post-mortems and maintenance window reviews.

How do I scope Auvik alerts to one MSP client tenant?

Pass the tenants parameter with the client name or domain prefix to restrict results to a single managed customer. Omitting the parameter queries across all visible tenants, which can mix alerts between clients.

What is the difference between dismissed and resolved Auvik alerts?

A resolved alert means Auvik determined the triggering condition cleared, while a dismissed alert was manually hidden in the Dashboard but may still indicate an unresolved condition. Use dismissed=false for triage and dismissed=true to audit what was silenced.