Skip to main content
Use the Webhook alert destination of Redash to send query alert state changes to Flashduty On-call. Each Redash alert maps to one Flashduty alert: it triggers when the query result meets the condition (TRIGGERED) and recovers automatically when it returns to normal (OK). This applies to self-hosted Redash.

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 Redash, 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 Redash 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 Redash

You need Redash administrator privileges to create an alert destination, and the Redash server must be able to reach the Flashduty push URL.
1

Create a Webhook alert destination in Redash

Where: Redash › Settings › Alert Destinations › New Alert DestinationThen click Create.
2

Add the destination to a Redash alert

Where: Redash › Alerts › Destinations › AddOpen an existing alert, or create one: choose a published query without parameters, then set the Value column, condition, and threshold.Save the alert. Recovery needs no separate setting: when the alert status changes from TRIGGERED back to OK, Redash notifies the same destination and Flashduty recovers the alert.
3

Trigger and confirm an alert

  1. Make the query result meet the alert condition, wait for the query to run on its refresh schedule, and confirm Flashduty receives an active alert
  2. Make the query result return to normal and confirm the alert recovers
Let the alert fire for real once. After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

Alert key

Flashduty uses the Redash alert ID (alert.id) as the Alert Key. The trigger, repeated notifications, and recovery of one Redash alert share one Alert Key. Changes to the alert name, condition, threshold, or state do not change it. A request without alert.id is rejected. Connect only one Redash instance to each Flashduty integration: alert IDs repeat across instances, so create a separate integration for each.

Status and severity

Redash notifications carry no severity, so Flashduty acts on the alert state: unknown means the query has no data to evaluate. Redash notifies only when the state changes, or when a triggered alert passes its repeat interval; an alert whose first evaluation is OK sends no notification.

Labels

Troubleshooting

  • Flashduty receives no alert: confirm the alert has the Webhook destination, is not muted, and its query is published and runs on a refresh schedule (on a self-hosted Redash the worker must consume the periodic and scheduled_queries queues, which the default configuration does). Redash times the request out after 5 seconds and does not retry; failures appear only in the Redash log
  • Flashduty returns an invalid-parameter error: confirm the URL is complete and includes integration_key
  • The alert does not recover: Redash sends the recovery only when the state becomes OK; while the query has no data the state is unknown and the alert stays open
  • No repeated notifications: When triggered, send notification is set to Just once
For more details, see the Redash alerts documentation.