Skip to main content
Use the Webhook integration of Auvik to send alerts on devices, interfaces, networks, and services to Flashduty On-call. Auvik posts one notification when an alert is triggered and one when it is cleared. Flashduty links both with the same Alert Key: the trigger creates an alert and the clear recovers it.

In Flashduty On-call

You can get the integration push URL in either of the following ways.

Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select Auvik, then click Save
  4. Open the generated integration card and copy the Push URL

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Auvik and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

Configure Auvik

Webhook integrations can be managed only from the MSP global view in Auvik, and you need the matching administrative permission. The webhook URL must use HTTPS, which the Flashduty push URL does.
1

Add a Webhook integration in Auvik

Where: Auvik › Integrations › Add Integration › WebhookClick Test Connection. Auvik posts {"my-api-test-field": "my-api-test-value"} to the URL, and Flashduty returns success without creating an alert. This only proves the URL is reachable, not that a real alert will parse. Then click Save.
2

Create a notification channel and associate it with alerts in Auvik

Where: Auvik › Manage Alerts › Notification Channels › Add Notification ChannelAuvik sends only the alerts that are associated with a notification channel:Save it, then associate the notification channel with the alerts you want to send to Flashduty, from the global view or a site view. Auvik posts again by itself when an alert is cleared, so no separate recovery setup is needed.
3

Trigger an alert and confirm

Where: Auvik › Manage AlertsLet an alert that uses the notification channel fire in Auvik. After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works. When the condition recovers and Auvik clears the alert, the Flashduty alert recovers automatically.
Auvik requires standard English characters in organization names. Webhook alerts may not be delivered as expected otherwise. You can change the name under Admin → Settings → Organization.

Alert key

Flashduty uses correlationId from the notification as the Alert Key. Auvik documents it as the unique API identifier of the alert trigger. The triggered and cleared notifications of one alert carry the same correlationId but different alertId values, so Flashduty does not use alertId. Changes to the alert name, severity, description, or time do not change the Alert Key. A notification that has a status but no correlationId is rejected.

Status and severity

Flashduty derives the status from alertStatusString (or alertStatus when the string is missing) and the severity from alertSeverity (or alertSeverityString when the number is missing): A missing or unrecognized severity is treated as Warning.

Labels

Troubleshooting

  • Test Connection fails: Confirm the webhook URL is complete, includes integration_key, and uses HTTPS
  • No alerts arrive: Confirm the notification channel is associated with the alerts and uses this Webhook integration as its contact method
  • The alert does not recover: Auvik posts a Cleared notification only when it clears the alert. If the alert is dismissed or deleted in Auvik, close it manually in Flashduty
  • Flashduty returns an invalid parameter error: The notification has a status but no correlationId, or the status is neither Triggered nor Cleared. Make sure no JSONata transformation is configured
For field details, see How do I interpret Auvik webhook notifications? and Integrating Auvik with a webhook.