Prometheus Integration Guide

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.

In AlertManager

Step 1: Configure Alertmanager

Locate and open the configuration file, typically alertmanager.yml in the Alertmanager deployment root directory

In the receivers configuration section, add a Flashduty webhook type receiver as follows:

receivers:
- name: 'flashcat'
  webhook_configs:
  - url: '<Your Integration Push URL>'
    send_resolved: true

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:

receivers:
- name: 'flashcat'
  webhook_configs:
  - url: '<Your Integration Push URL>'
    send_resolved: true
    http_config:
    proxy_url: 'http://proxyserver:port'

In the route configuration section, change the default route to specify the newly configured webhook receiver:

route:
  receiver: 'flashcat'

If you don't want to affect existing push channels, you can add the receiver to a route's subroute:

route:
 receiver: 'feishu'
 - routes:
   receiver: 'flashcat'

Save the configuration file

Reload the configuration (by sending a SIGHUP signal to the process or POST request to /-/reload api)

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.

Open the alert rules configuration file

For each alert rule, modify the annotations section by adding a timestamp field:

annotations:
  timestamp: '{{ with query "time()" }}{{ . | first | value }}{{ end }}'
  ...

Save the configuration file

Reload the configuration (by sending a SIGHUP signal to the process or POST request to /-/reload api)

Done

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, the system automatically sets the Prometheus alert severity to Warning.

Prometheus to Flashduty severity mapping:

Prometheus	Flashduty	Status
critical	Critical	Critical
warning	Warning	Warning
warn	Warning	Warning
info	Info	Info
acknowledged	Info	Info
unknown	Info	Info
unk	Info	Info
ok	Ok	Ok

FAQ

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, simply configure routing rules to your desired channel.

In AlertManager

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 subroutes, ensure your routing is correct (e.g., if previous routes set continue, AlertManager will skip matching subsequent subroutes. 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, modify the Alert Rules 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.

If you still can't identify the root cause after following these steps, please contact us directly.

Prometheus Integration

Requirements

In AlertManager

Supported Versions

Setup Steps

In Flashduty

Using Private Integration

Using Shared Integration

In AlertManager

Step 1: Configure Alertmanager

Step 2: Configure Timestamp

Severity Mapping

FAQ

In Flashduty

In AlertManager

Prometheus Integration

Requirements#

In AlertManager#

Supported Versions#

Setup Steps#

In Flashduty#

Using Private Integration#

Using Shared Integration#

In AlertManager#

Step 1: Configure Alertmanager#

Step 2: Configure Timestamp#

Severity Mapping#

FAQ#

In Flashduty#

In AlertManager#

Requirements

In AlertManager

Supported Versions

Setup Steps

In Flashduty

Using Private Integration

Using Shared Integration

In AlertManager

Step 1: Configure Alertmanager

Step 2: Configure Timestamp

Severity Mapping

FAQ

In Flashduty

In AlertManager