Heplon

Connect Prometheus

This guide covers what to put into the connector form for Prometheus.

1. Find the API URL

Use the base URL of the Prometheus HTTP API, with no path. Heplon appends /api/v1/... itself.

https://prometheus.example.com

The URL must be reachable from the internet.

2. Choose the endpoint authentication

Prometheus has no bearer-token authentication of its own. The connector form offers three exclusive choices.

ChoiceUse it when
NoneThe URL points at Prometheus directly and the endpoint is open to Heplon.
Static bearer tokenA proxy in front of Prometheus accepts a fixed token.
OAuth 2.0 access profileA gateway in front of Prometheus validates JWT bearer tokens, for example OAuth2 Proxy in front of Keycloak.

Since the Prometheus endpoint is reachable from the internet, the URL likely points at a proxy in front of Prometheus, such as an authenticating reverse proxy (nginx, Envoy, OAuth2 Proxy), or at Thanos Query or Grafana Mimir behind one.

With a static token, Heplon sends it as Authorization: Bearer <token>. With an access profile, Heplon gets an access token from your identity provider and sends that instead, renewing it before it expires. One profile can serve both this connector and your Loki connector. To create a profile, see Create an HTTP access profile. That page also explains how to read a failed health check.

A service that expects basic auth or AWS SigV4 (Grafana Cloud, Amazon Managed Service for Prometheus) is currently not supported. We will add support once the first customer asks for it.

3. Fill in the form

In Heplon, open Connectors, select Add connector, then Prometheus.

FieldValue
Namean arbitrary name
API URLthe URL from step 1
Endpoint authenticationthe choice from step 2, with its token or profile

Prometheus is now connected to Heplon.