Skip to main content
Sync Splunk alert events to Flashduty through webhook.

In Flashduty On-call

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

Use a dedicated integration

Choose this option if all alerts go to one channel. It’s the simpler setup.
  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Choose Splunk integration and click Save to generate a card
  4. Open the generated integration card and copy the Push URL

Use a shared integration

Choose this option if you need to route alerts to different channels based on the alert payload.
  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Splunk integration:
    • Integration Name: Define a name for this integration
  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

In Splunk

1

Save a search as an alert in Splunk

Where: Splunk Web › Search & Reporting › Search › Save As › AlertIn the Search & Reporting app, search for the keywords you want to monitor (for example “error”), then choose Alert from the save menu in the upper right corner to configure the search as a monitoring item.drawingIn the popup, enter a name and configure the set up and Triggering conditions sections according to your needs.
2

Add a webhook trigger action to the alert

Where: Splunk Web › Save As Alert dialog › Trigger Actions › Add Actions › WebhookClick Save to finish the alert configuration.drawingdrawingSplunk Enterprise 9.0 and later and Splunk Cloud Platform 8.2203 and later require the webhook URL to be on the webhook allow list, otherwise the request is not sent. A user with the admin role or the edit_webhook_allow_list capability can add it; see the Splunk documentation.
3

Trigger the alert and confirm

Where: Splunk Web › Search & Reporting › AlertsThe Splunk webhook action has no test button. Wait for the alert to match its trigger condition, which produces a real alert. Splunk alerts always arrive as Warning and produce no recovery event (see “Status and severity” below).After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

Status and severity

Since Splunk alert events don’t differentiate severity levels, all alert events pushed from Splunk to Flashduty will have a Warning status and won’t include recovery events. Turn on the auto-close timeout for the channel that receives this integration (Flashduty console › Channels › Configuration › Settings › Advanced Settings), 24 hours recommended; see auto-close timeout.