Prometheus-compatible metrics

Prometheus-compatible metrics

Scrape scoped measurements and distinguish collection gaps from measured idle capacity.

Infra exposes Prometheus-compatible measurements for external monitoring. Scrape access is scoped to an organization or permitted project selection and does not grant infrastructure mutation permission.

Configure a scrape target

Create an exporter credential with metric-read access and obtain its endpoint from Observe → Exporters. Restrict the credential to required resource scopes. The endpoint uses the control-plane origin or the installation's approved observation gateway. Add a scrape job to your Prometheus configuration:

YAML
scrape_configs:
  - job_name: infra
    scheme: https
    metrics_path: /api/v1/organizations/org_main/metrics/prometheus
    authorization:
      type: Bearer
      credentials_file: /run/secrets/infra-metrics-token
    static_configs:
      - targets: [infra.example.com]

The file must contain an exporter-authorized token. Keep it outside repository configuration. A node host address is not a substitute for the scoped control-plane exporter URL.

Samples and identity

Metric names and units are listed by the exporter catalog. Labels include stable resource IDs and the permitted location dimensions. Display names can change; alerts should not identify a persistent resource only by its mutable name.

Supported node and droplet sources collect raw observations every 5 seconds by default. Installation and agent settings can select a longer interval. A shorter scrape interval does not force another agent sample. Older data can be aggregated under retention policy.

Missing series

An absent or stale source is not emitted as a fresh zero. Configure no-data rules alongside threshold rules. Counter resets can occur after component replacement; use the monitoring system's rate calculation rather than treating a reset as negative traffic.

Cardinality and permission changes

Export only required label dimensions. Arbitrary high-cardinality project labels can increase monitoring storage and query cost. Revoking a project's read access removes its future visible samples; it does not erase values already retained by the external monitoring system.

Use metric queries for bounded historical reads and anomaly detection for Infra-managed baseline evaluation.

Export request

GET/organizations/{organization_id}/metrics/prometheus
Scope
metrics:read
Auth
Bearer API key

Returns Prometheus-compatible exposition for the caller's permitted resource scope. The request path is relative to /api/v1; a scrape uses the configured control-plane origin. Unavailable source samples are not replaced by fresh zeros. Disabling export removes this surface without disabling ordinary resource metrics.