LandfallDocs
Integrations · Telemetry

Prometheus

Connect your own Prometheus (self-hosted or otherwise) as a queryable source the investigator agent reads from during an incident, the same way it reads Datadog or Coralogix.

Connecting a Prometheus as a queryable source

An organization connects Prometheus the same way every other telemetry source is connected: through the integrations wizard. Once connected, the investigator agent can query it during an incident with zero source-specific agent code — the same dynamic-discovery mechanism every other source uses (see Integrations architecture).

Prometheus
Base URL (+ optional auth)
→
Landfall
Settings → Integrations

What you'll need

  • A Prometheus server reachable FROM Landfall — a real constraint worth stating plainly. A Prometheus running inside your own private network is typically not reachable from a hosted Landfall the way a public SaaS API (Datadog, Coralogix, Sentry) is — this is a genuine limitation of Prometheus as a source, not an oversight.
  • An admin on your Landfall organization, to save the connection under Settings → Integrations.

  1. Settings → Integrations → Prometheus

    Enter your Prometheus server's base URL. If it sits behind auth, add either a bearer token or a basic-auth username/password — leave both blank for an unauthenticated instance (the common case for a self-hosted Prometheus already inside a private network).

    Settings → Integrations → Prometheus
    Landfall's Prometheus integration panel: a Base URL field, optional Bearer token field, optional basic-auth username/password fields, and a Test connection button.

  2. Test connection

    Landfall calls your Prometheus's own /api/v1/status/buildinfo endpoint before saving anything — a cheap, read-only call that exists purely to answer "is this actually a reachable Prometheus." A server that can't be reached, or that rejects the supplied credentials, is refused outright rather than stored as "configured but unverified."

    Settings → Integrations → Prometheus
    Landfall's Prometheus integration panel showing a green connected status and the message Prometheus reachable at http://prometheus:9090.

  3. Save integration

    Prometheus now shows Configured alongside your organization's other connectors, and appears in the capability listing an incident's investigator (human or Beacon) can query against.

    Settings → Integrations
    Landfall's Integrations list showing the Prometheus tile with a green Configured status alongside Datadog, Coralogix, and AWS.
Test connection failed?
  • Confirm the base URL is reachable FROM wherever core-api runs, not just from your own browser/laptop — the two are frequently on different networks.
  • If your Prometheus requires auth, confirm you've set exactly one of bearer token OR basic auth; a bearer token takes precedence when both are present.
  • The base URL should be the origin only (e.g. http://prometheus.internal:9090) — Landfall appends /api/v1/… itself.

Alerting → incidents

Connecting Prometheus (above) lets the investigator agent read your metrics during an investigation. Opening an incident automatically the moment a Prometheus alerting rule fires is a separate, independent capability — Prometheus's own Alertmanager, not Prometheus itself, is what calls Landfall. See Triggering Integrations → Alertmanager for that setup. The two are independent; most teams eventually set up both.

Reference

FieldValue
Base URLYour Prometheus server's origin, reachable from Landfall — required
Bearer tokenOptional; sent as Authorization: Bearer
Basic auth username/passwordOptional; ignored when a bearer token is set
Read operationslistMetrics (discover what metric names exist — /api/v1/label/__name__/values), instantQuery (/api/v1/query), rangeQuery (/api/v1/query_range, for correlating a metric against an incident's time window), listAlerts (/api/v1/alerts)