Adding a Prometheus Alertmanager data source lets Grafana open an existing Alertmanager from the Alerting UI. Use it when Prometheus or another alert producer already sends alerts to Alertmanager and operators need Grafana to inspect alert state or create silences without leaving the Grafana interface.
Grafana includes a built-in Alertmanager data source type with Prometheus and Mimir implementation modes. For a Prometheus implementation, Grafana can manage silences, while contact points, notification policies, and templates remain read-only because the Prometheus Alertmanager API does not update those resources.
The URL must be reachable from the Grafana server because only Server access mode is functional for this data source. Use a service name such as alertmanager:9093 in container or Kubernetes deployments, or use the routed HTTPS endpoint when Alertmanager is outside the Grafana network.
Related: How to add a Prometheus data source in Grafana
Related: How to test a Grafana data source
Related: How to create a Grafana alert silence



Mimir is the default implementation in new Grafana data source forms. Use Prometheus for the standalone Prometheus Alertmanager service.
Forwarding Grafana-managed alerts also requires enabling the Alertmanager from Alerting settings after the data source is saved.
http://alertmanager.example.internal:9093
In separate containers, localhost points inside the Grafana container. Use the Docker service name, Kubernetes service DNS name, or another server-reachable address instead.

Do not enable Skip TLS Verify for production endpoints unless certificate validation is intentionally handled outside Grafana.
The health check proves Grafana can reach the Alertmanager API through the saved data source settings.
If multiple Alertmanagers are configured, choose Prometheus Alertmanager before creating or reviewing silences. Prometheus Alertmanager contact points, notification policies, and templates remain read-only from Grafana.