# Auvik

> Network device context and alert history beside the component they explain.

Link an Auvik Network Management device to the stratum for a switch, firewall,
server or other component in your diagram. The saved panel helps readers identify
the device, understand its network context and review recent alert events. Open
Auvik for its current dashboards, detailed investigation and operational actions.
Continuum Link does not redraw the diagram.

This connection uses **Auvik Network Management**. It does not import Auvik SaaS
Management applications, users, licences or security logs.

## Connect and select sites

1. You need an Enterprise licence, edit access to the blueprint and
   `continuum_integrations.manage` on the connection's organisation or team.
2. Create a dedicated Auvik service account with a custom API-only role and access
   to the intended sites. Give it read access to **API – Device info**,
   **API – Alerts** and **API – Tenants**. Auvik's built-in **Read Only** role does
   not grant these API permissions, and its built-in **API Access Only** role
   grants unrelated reads and tenant editing. Build a custom role with only the
   reads listed above. See
   [Auvik's service-account guidance](https://support.auvik.com/hc/en-us/articles/48529381648660-API-Access-Only-Role-and-Service-Account-Configuration-in-Auvik).
3. In Auvik, open **My Profile → Manage API Credentials** and generate the key.
   In Blueprintr, open **Settings → Continuum** on the organisation or team, go
   to **Operational integrations**, choose **New integration**, and select
   **Auvik** as the **Type**. Give the connection a **Name**, then enter
   **Region**, **Username** and the API key.
4. Review **Auvik snapshot audience**, **Saved detail** and the optional sections,
   then choose **Connect & verify**. To restrict the connection to named sites,
   select **Configure** on its row afterwards and open **Auvik site scope**. Clear
   **Include every accessible site**, choose **Load Auvik sites**, tick the sites,
   then choose **Verify & save settings**. Ticking a site does not save it on its
   own. **Exact site IDs** accepts up to 25 comma-separated leaf-site IDs
   instead. Changing the region or username requires saving and verifying again
   before the site list will load.
5. Save the blueprint and open the relevant stratum's **Continuum Link** controls.
   Search by device name, IP address, serial number or stable Auvik API ID and
   review the site, identity and matching evidence before linking.
   **Suggest integrations…** on a shape and **Scan for integrations** across the
   blueprint both offer candidates; selecting one is still an editor decision.

> [!IMPORTANT]
> **Region** is the cluster label in your Auvik **API** hostname,
> `auvikapi.<region>.my.auvik.com`, for example `us1` or `eu1`. It is not your
> customer domain and it is not a URL. Entering a URL is refused with "Enter the
> Auvik cluster region, such as us1; do not enter a URL."

**Include every accessible site** includes current and future sites accessible
to the Auvik service account. Clear it and select exact sites to keep a connection
focused on one customer or environment. The list uses Auvik's site labels or
domain prefixes alongside stable IDs.
Selecting a parent organisation is not a substitute for selecting its leaf sites.
Device names and private IP addresses can repeat across sites: check the site and
stable device ID before attaching a panel.

Verification checks inventory and alert access for each explicitly selected
site. Optional capabilities are checked on one representative site; the result
names that site. The first fetch and later refreshes check the actual linked
device and available data, so a verified connection can still have unavailable
optional observations on another device or site.

## Choose the saved information

| Setting | Default | What it changes |
| --- | --- | --- |
| Auvik snapshot audience | Blueprint editors | Keeps the imported panel visible to blueprint editors. Choose **All Blueprint readers** only after approving the information for everyone who can read the blueprint. Unlike Datadog, LogicMonitor and Rootly, Auvik's reader option carries no "approved metadata" suffix. |
| Saved detail | Summary | Keeps device/site identity, monitoring state, hardware, firmware and event counts. Detailed mode also permits internal IP addresses, serial numbers, network identities and alert names; review the resulting preview before sharing it. |
| Interfaces and connected peers | Off | Adds counts of disabled/impaired interfaces and history for up to two selected enabled interfaces with known peers. Detailed mode also shows up to 12 important interfaces with available peer/network relationships. Requires read access to **API – Interface info**. |
| Maintenance context | Off | Adds available running-configuration backup metadata and lifecycle context. Requires the corresponding device-detail and hardware-lifecycle reads. Configuration bodies are not imported. |
| Performance summary | Off | Adds device availability/outage and interface utilization/discard observations over the previous 24 complete UTC hours. The Auvik account must expose the statistics and the service account must be permitted to read them. |
| Alert history period | 7 days | Chooses a 1-, 7- or 30-day history window. This does not define which alerts are currently active. |

Optional sections can be unavailable because of account permissions, discovery
coverage or product availability. They do not require write access. Ask the Auvik
administrator to grant the specific read permission or leave the section off;
granting an administrative role is unnecessary.

## Read the panel in context

The device status is Auvik's observation at the fetch time. An online device can
still have a fault, and a device marked unmanaged is not evidence of monitoring
coverage. Missing information means unknown or unavailable, not healthy.

Alert history contains events that Auvik recorded during the selected window.
Created, resolved, paused and unpaused events retain their meanings. A created
event is not presented as proof that its alert is still active. Dismissal and
dispatch are separate properties. Use the event's source link to check the
current record in Auvik when using Detailed mode; Summary retains event counts
and the device's dashboard link. The detailed timeline shows the most recent 20
retrieved events, and the scope states which interfaces were included. Detailed
mode also caps the network membership table at 20 networks and the address list
at 12, each with a coverage row stating what was omitted.

Interfaces distinguish whether a port is administratively enabled from its
observed operational state. An administratively disabled port is different from a
failed uplink. Peer and network relationships describe Auvik's discovered
inventory; they do not establish that a route is reachable or that redundancy
will work.

Maintenance information helps prepare a replacement or change. A backup timestamp
does not prove that a restore will succeed. Lifecycle information can include
Auvik's information provider, confidence and source links; review those sources
before treating a predicted end-of-support date as a vendor commitment.

Performance observations cover the previous 24 complete UTC hours with hourly
samples. The panel states its period and units; missing hours remain gaps, and
an hourly average is not an instantaneous measurement or a service availability
guarantee.

## Refresh and recover

Opening the tab shows its saved snapshot. Re-fetch with the circular-arrows icon
on the linked row ("Re-fetch this integration's data"). After
five minutes the snapshot is due for refresh; this is a reminder, not automatic
polling. A failed refresh retains the previous snapshot with a warning. An
unreadable or incomplete optional section is labelled rather than turned into
zero alerts or a successful check.

If access fails, check the account's API role, selected sites and region. An
Auvik account move can require a new region. Unlink every linked Auvik device
before changing it: "Unlink existing Auvik devices before changing region, then
review and link their identities in the new region." For a rate limit, wait before
refreshing again. Choose **Rotate token** on the connection's row, then **Verify & replace**, which
verifies a replacement credential before it swaps. A replacement is refused when
more than 50 linked Auvik identities need checking;
**Suspend** stops search and refresh while leaving snapshots readable, and the
broken-link icon removes the current binding. Delete a
connection after removing its bindings.

Site or credential changes must preserve access to existing links. If a new scope
excludes a linked site, keep it selected or unlink that device first. Older links
without a saved site identity need to be reviewed and linked again before their
scope or credential identity can change.

## Sharing and retained copies

The panel is fetched with the service account's access. Readers do not need their
own Auvik account to see an approved reader-visible snapshot. Opening a source
link still requires their own Auvik access.

Editor-only panels use Blueprintr's existing audience controls for readers,
embeds, viewer exports and search/AI indexing. Approved reader-visible content
follows the blueprint's audience, including the public on a public blueprint.
Editor exports and backups can retain the source information.

Settings apply to later fetches. They do not retract previous exports, version
history, templates or other independent copies, or redact authored titles and
notes outside the managed panel. Review those separately before publishing.
Revoking a key, suspending a connection or unlinking does not recall existing
copies.

Before operational use, compare a known device and its history with your own
Auvik account, confirm the selected sites and optional permissions, and check
the reader view. Some Auvik API capabilities are documented as beta. Local tests
do not establish your account's access or live data completeness.