Skip to main content
Sync Skywalking 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 Skywalking 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 Skywalking 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 Skywalking

1

Add a level tag to the alarm rules

Where: Skywalking OAP server › ./config/alarm-settings.yml › rulesLog in to the Skywalking server and open ./config/alarm-settings.yml. Add tags.level to each alarm rule; Flashduty uses it to set the severity.
2

Add the Flashduty webhook URL and restart

Where: Skywalking OAP server › ./config/alarm-settings.yml › bottom of the filePick the syntax for your Skywalking version; the URL is {integration_url}:
Save the file and restart the Skywalking service to apply it.
3

Trigger an alarm and confirm

Where: Skywalking OAP server › ./config/alarm-settings.ymlSkywalking has no webhook test entry. Wait for the expression of a configured rule to match, which produces a real alarm.After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

Status and severity

Skywalking sends no recovery notification, so Flashduty does not recover these alerts automatically. 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.