All integrationsMonitoring

Auvik

Work with Auvik network monitoring: read clients, devices, interfaces, networks, configuration backups, components, warranties and lifecycles, list and dismiss alerts, pull device, interface and service statistics, and start workflows on new or cleared alerts, new or offline devices, configuration changes and failing components.

actions
25
triggers
6

Triggers

Start a workflow when something happens in Auvik.

  • New alertRuns when Auvik raises an alert, with its severity, what it is about and a link to it. Alerts raised before the workflow is turned on don't start it. With Auvik's webhook set up (see the connection's steps) it starts within seconds; without it, how often it checks follows your workspace plan.
  • Alert clearedRuns when an Auvik alert clears (the problem is resolved), with what it was about. Alerts cleared before the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • New deviceRuns when Auvik discovers a new device, with its type, make and model and IP addresses. Devices already there when the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • Device went offlineRuns when a device Auvik monitors goes offline, with when it was last seen. Devices already offline when the workflow is turned on don't start it, and a device starts it again each time it goes offline. How often it checks follows your workspace plan.
  • Configuration changedRuns when Auvik backs up a device's changed configuration, with the device and when. Backups taken before the workflow is turned on don't start it. How often it checks follows your workspace plan.
  • Component degraded or failedRuns when a device component (a fan, disk, power supply, CPU or memory) becomes degraded or fails. Components already in that state when the workflow is turned on don't start it, and one starts it again each time it goes from OK to degraded or failed. How often it checks follows your workspace plan.

Actions

Steps a workflow can run in Auvik.

  • List clientsList the clients and multi-clients (Auvik's tenants) your Auvik user can see, with their ids and domain prefixes.
  • List client detailsList every client under your main Auvik account with its display name, type, subscription, trial dates and address.
  • Get client detailsGet one client's display name, type, subscription, trial dates and address.
  • List devicesList devices Auvik has discovered, with their type, make and model, IP addresses, firmware and online status, filtered by client, type, status, vendor or network. Gets one page; to see more, run it again with the next page it gives.
  • Get deviceGet one device: its name, type, make and model, serial number, IP addresses, software and firmware, when it was last seen and whether it is online.
  • List device warrantiesList devices' warranty and service coverage, warranty end dates and recommended software versions. Gets one page; to see more, run it again with the next page it gives.
  • Get device warrantyGet one device's warranty and service coverage, warranty end date and recommended software version.
  • List device lifecyclesList devices' end of sale, software maintenance, security maintenance and last support status, to plan replacements. Gets one page; to see more, run it again with the next page it gives.
  • List interfacesList device interfaces (ports) with their type, MAC and IP addresses, speed and status, filtered by device, type or status. Gets one page; to see more, run it again with the next page it gives.
  • Get interfaceGet one interface: its type, MAC and IP addresses, speed, duplex, status, device and what it connects to.
  • List networksList networks Auvik has discovered (routed, VLAN, Wi-Fi and more), filtered by type, scan status or device. Gets one page; to see more, run it again with the next page it gives.
  • Get networkGet one network: its name, type, scan status and the devices on it.
  • List configuration backupsList the configuration backups Auvik took of devices, with when each was taken and whether it is the running configuration. Gets one page; to see more, run it again with the next page it gives.
  • Get configuration backupGet one configuration backup: its device, when it was taken and whether it is the running configuration.
  • List componentsList device components (CPUs, disks, fans, memory, power supplies and system boards) and whether each is OK, degraded or failed. Gets one page; to see more, run it again with the next page it gives.
  • Get componentGet one component: its name, type, device and whether it is OK.
  • List notesList the notes people left in Auvik on clients, devices, networks and interfaces, with who changed each last. Gets one page; to see more, run it again with the next page it gives.
  • List remote session auditsList the remote sessions (tunnels, terminals and remote browsers) people opened to devices through Auvik, with who, when and how each ended. Gets one page; to see more, run it again with the next page it gives.
  • List alertsList alerts Auvik raised, with their severity, status, description and what they are about, filtered by client, severity, status or time. Gets one page; to see more, run it again with the next page it gives.
  • Get alertGet one alert: its name, severity, status, description, when it was detected, what it is about and any ticket it was sent to.
  • Dismiss alertDismiss an alert, as a technician would in the Auvik dashboard.
  • Get device statisticsGet bandwidth, CPU, memory, storage or packet figures for devices over a period, one data point per minute, hour or day.
  • Get device availabilityGet uptime or outage figures for devices over a period, one data point per minute, hour or day.
  • Get interface statisticsGet bandwidth, utilization, packet loss, discard or packet figures for interfaces over a period, one data point per minute, hour or day.
  • Get service statisticsGet ping time or ping packet figures for the services Auvik monitors (such as its internet connection check) over a period.

Automate Auvik with Lodol.

Connect Auvik, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.