Prometheus Alertmanager (v2) extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Receive Prometheus Alertmanager events and open problems in Dynatrace.
Get started
Overview
Receive Alertmanager events and turn them into Dynatrace problems with the 
Prometheus Alertmanager (v2) extension.
Activation and setup
-
ind the extension in Dynatrace Hub to start the installation.
-
In Dynatrace, create a monitoring configuration for
Prometheus Alertmanager (v2) extension.
The extension should run on a single 
ActiveGate instance.
Later, you need to configure Prometheus Alertmanager to send events to this specific ActiveGate instance.
The parameters are:
-
Group name - A user-friendly group name for the custom devices.
-
API Token - A token to create custom devices, read and write problems such as
DataExport,problems.read,problems.write,events.ingest. -
Listening Port - The port where ActiveGate listens. Alertmanager needs to reach this port.
-
Problem opening severities - The list of severity labels that send problem opening events, for instance, the critical label. All other severity labels send a Custom Info Events label instead.
-
In Alertmanager, create a webhook config where the url field points to the Dynatrace ActiveGate, for example,
http://<my.ag.ip.address>:9393/webhook.Example receiver configuration
receivers:- name: 'dynatrace'webhook_configs:- url: 'http://100.94.253.97:9393/webhook'The endpoint always ends in /webhook.
Problems are only created for alerts where label called severity matches the ones configured in Dynatrace.
All other alerting options and routes are to be configured in Alertmanager.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
Troubleshooting
You can troubleshoot the integration by sending a POST request directly to the ActiveGate:
curl -H 'Content-Type: application/json' -d '{"receiver": "dynatrace", "status": "firing", "alerts": [{"status": "firing", "labels": {"alertname": "TargetDown", "namespace": "kube-system", "service": "kubelet", "severity": "warning"}, "annotations": {"message": "11.11% of the kubelet/kubelet targets in kube-system"}, "startsAt": "2021-03-19T01:35:45.72Z", "endsAt": "0001-01-01T00:00:00Z", "generatorURL": "http://openshift.com", "fingerprint": "e425bb91067b6c9e"}], "groupKey": "{}:{alertname=\"Test Alert\", cluster=\"Cluster 02\", service=\"kubelet", "groupLabels": {"alertname": "Test Alert", "cluster": "Cluster 02", "service": "Service 02"}, "commonLabels": {"alertname": "Test Alert", "cluster": "Cluster 02", "service": "Service 02"}, "commonAnnotations": {"annotation_01": "annotation 01", "annotation_02": "annotation 03"}, "externalURL": "http://8598cebf58a1:9093"}' http://<ACTIVEGATE_IP_ADDRESS>:9393/webhook
