Skip to main content
Push Prometheus alert events to Flashduty through AlertManager using webhooks. When an alert is triggered, it sends a trigger event to Flashduty, and when the alert recovers, it sends a recovery event.

​
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.

​
Supported Versions

This guide is compatible with Alertmanager 0.16.0 and above.

​
Setup Steps

​
In Flashduty

You can obtain an integration push URL through either of these two methods:

​
Using Private Integration

Choose this method when you don’t need to route alert events to different channels. It’s simpler.

​
Using Shared Integration

Choose this method when you need to route alert events to different channels based on the alert payload.

​
In AlertManager

​
Step 1: Configure Alertmanager

  1. Log in to your Alertmanager instance
  2. Locate and open the configuration file, typically alertmanager.yml in the Alertmanager deployment root directory
  3. In the receivers configuration section, add a Flashduty webhook type receiver as follows:
    Replace the url parameter value with your integration push URL, ensuring the integration_key is included in the query string parameters. If you need to request Flashduty through a proxy, you can additionally set the http_config proxy_url parameter:
  4. In the route configuration section, change the default route to specify the newly configured webhook receiver:
    config
    If you don’t want to affect existing push channels, you can add the receiver to a route’s subroute:
    config
  5. Save the configuration file
  6. Reload the configuration (by sending a SIGHUP signal to the process or POST request to /-/reload api)
  7. Done

​
Step 2: Configure Timestamp

By default, the system uses the current time as the event trigger time. If you want to customize the time, you can set an additional timestamp field to identify the exact time of each alert.
  1. Log in to your Prometheus Server instance
  2. Open the alert rules configuration file
  3. For each alert rule, modify the annotations section by adding a timestamp field:
  4. Save the configuration file
  5. Reload the configuration (by sending a SIGHUP signal to the process or POST request to /-/reload api)
  6. Done

​
In Volcengine Managed Prometheus (VMP)

VMP’s general webhook sends alerts in the Alertmanager format, so it uses this integration’s push URL directly.
  1. Log in to the Volcengine Managed Prometheus console, go to Alert Center → Alert Notification Policies, and open the Notification Objects tab
  2. 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
  3. Add the contact to a contact group (VMP notification policies only accept contact groups)
  4. In Alert Notification Policies, create or edit a policy and select that contact group as the notification object
  5. 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.
VMP’s alertname label is the alert rule’s UUID, so the default alert title is a UUID. The rule name is in the alerting_rule_name label; set this integration’s Title Rule to use $alerting_rule_name.

​
Severity Mapping

The system extracts severity, 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