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.

Steps to add a Prometheus Alertmanager data source in Grafana:

  1. Open Main menuConnectionsData sources.
  2. Click Add data source.
  3. Enter Alertmanager in Filter by name or type.
  4. Click Alertmanager.
  5. Set Name to a descriptive value such as Prometheus Alertmanager.
  6. Select Prometheus under Implementation.

    Mimir is the default implementation in new Grafana data source forms. Use Prometheus for the standalone Prometheus Alertmanager service.

  7. Keep Receive Grafana Alerts disabled unless this Alertmanager should receive all Grafana-managed alerts.

    Forwarding Grafana-managed alerts also requires enabling the Alertmanager from Alerting settings after the data source is saved.

  8. Enter the Alertmanager URL that the Grafana server can reach.
    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.

  9. Keep Access set to Server (default).
  10. Enable Auth or TLS options only when the Alertmanager endpoint requires them.

    Do not enable Skip TLS Verify for production endpoints unless certificate validation is intentionally handled outside Grafana.

  11. Click Save & test and confirm that Grafana shows Health check passed.

    The health check proves Grafana can reach the Alertmanager API through the saved data source settings.

  12. Open Main menuAlertingSilences.

    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.