Requirements
In AlertManager
- You must have permission to modify the AlertManager configuration file.
- Your AlertManager server must be able to access api.flashcat.cloud domain to push alerts to the internet.
- The request body of a single push must not exceed
10 MiB; larger bodies are rejected with HTTP 413.
Supported versions
This guide is compatible with Alertmanager 0.16.0 and above.Setup steps
In Flashduty
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.View dedicated integration setup steps
View dedicated integration setup steps
- In the Flashduty console, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration, and enter the integration page
- Select Prometheus Alertmanager integration, click Save to generate a card
- Open the generated integration card and copy the Push URL
Use a shared integration
Choose this method when you need to route alert events to different channels based on the alert payload.Configure Alertmanager
1
Add a Flashduty receiver in alertmanager.yml
Where: alertmanager.yml › receivers (the file is usually in the Alertmanager deployment root directory)If Alertmanager reaches Flashduty through a proxy:
alertmanager.yml
alertmanager.yml
2
Route alerts to Flashduty in alertmanager.yml
Where: alertmanager.yml › routeTo send all alerts to Flashduty only, set the default route’s receiver to the receiver from the previous step:To keep your existing channels, add Flashduty as the first child route with
alertmanager.yml
continue: true. Child routes stop at the first match by default, and when any child route matches, the default route’s receiver no longer gets the alert, so list your existing channel as a child route too:alertmanager.yml
3
Reload the configuration on the Alertmanager host
Where: a terminal on the Alertmanager hostSave the file, check it, and reload it in either of these ways:
4
Send a test alert from Alertmanager and confirm
Where: a terminal on the Alertmanager hostAlertmanager pushes the alert after
group_wait (30 seconds by default). Then go back to Flashduty. If the integration shows a Latest event time, the setup works.Customize the event time
By default, the system uses the current time as the event trigger time. To use the time the alert actually fired, add atimestamp field to the annotations of each rule in your Prometheus alert rule files:
/-/reload).
Volcengine Managed Prometheus (VMP)
VMP’s general webhook sends alerts in the Alertmanager format, so it uses this integration’s push URL directly.- Log in to the Volcengine Managed Prometheus console, go to Alert Center → Alert Notification Policies, and open the Notification Objects tab
- Click Create Notification Object, set the object type to Contact, check General Webhook under Webhook (not the Feishu, DingTalk, or WeCom bot options, whose format is incompatible), enter the integration push URL, and leave Token unchecked
- Add the contact to a contact group (VMP notification policies only accept contact groups)
- In Alert Notification Policies, create or edit a policy and select that contact group as the notification object
- Select that notification policy in the alert rule’s notification settings, save, and you’re done
Volcengine is moving VMP alert notification to the Cloud Monitor alert center. According to Volcengine’s announcement, after October 12, 2026 alert configurations that have not been migrated are migrated automatically, and the old VMP alert notification APIs are taken offline gradually. After the migration, VMP alerts can reach Flashduty through the existing Volcengine Cloud Monitor Alert Events integration. Alternatively, use a Notification Callback template in the alert center that renders an Alertmanager-format webhook body, and push it to this integration.
Status and severity
The system extractsseverity, priority, and level from alert event labels in that order. The corresponding value will be used as Prometheus’s own alert severity. If none are found, it reads VMP’s internal_label_alert_level label: P0 maps to Critical, P1 to Warning, and P2 to Info. If that is also missing, the system sets the Prometheus alert severity to Warning.
Prometheus to Flashduty severity mapping:
FAQ
Why am I not receiving alerts in Flashduty?
Why am I not receiving alerts in Flashduty?
In Flashduty
- Check if the integration shows Latest Event Time. If not, Flashduty hasn’t received any pushes - prioritize checking the AlertManager section.
- If you’re using a Shared Integration, first confirm if you’ve configured Routing Rules. Without routing rules, the system will reject new pushes as there’s no channel to receive your alerts. In this case, configure routing rules to your desired channel.
- First, confirm if AlertManager has generated new alerts. If not, wait for new alerts to trigger and verify again.
- Open the AlertManager configuration file. If you’ve set up child routes, ensure your routing is correct (child routes stop at the first match by default, so a child route placed before Flashduty without
continue: truekeeps alerts from reaching Flashduty. We recommend setting only one default route to Flashduty). Also verify that the callback URL matches the integration push URL exactly. If they don’t match, fix the configuration and verify again. - If they match, confirm that your AlertManager instance can access api.flashcat.cloud domain. If not, you need to enable internet access or specifically allow access to Flashduty’s domain.
- If network access is fine, continue troubleshooting AlertManager by checking for relevant error logs.