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

Configure in Volcengine RTC

1

Create an alert rule in the Volcengine RTC console and enter the callback URL

Where: Volcengine console › Real-Time Communication › Monitoring › Alert Notifications › Alert Rules › Create RuleClick Confirm to finish.Volcengine RTC alert rule with Alert Callback checked and the push URL entered
2

Enable the rule and confirm

Where: Volcengine console › Real-Time Communication › Monitoring › Alert Notifications › Alert RulesFind the new rule in the list and click Enable. The rule takes effect only after it is enabled. Wait for the rule to trigger (you can lower the threshold temporarily to trigger it once).Back in Flashduty, the integration shows a Latest event time, which means the setup works.

Severity and event handling

Volcengine RTC alert callbacks carry no level: whether the rule level is Critical, Warning or Notice, Flashduty always maps it to Warning.
  • Every push gets a fresh alert key, so each callback is a separate alert.
  • The callback contains no recovery notice, so alerts never recover automatically and must be closed manually in Flashduty. (No-event detection only raises its own alert when RTC stops pushing entirely; it does not close these alerts.)
  • The alert title is <check>::<alert_type>, built from the callback’s check and alert_type values.
You can customize the severity through Alert Processing Pipeline.