Skip to content
Get startedRequest a demo
Databases, lakes, and warehouses

Prometheus

Self-managed or managed (Grafana Cloud, Amazon Managed Prometheus, Thanos)

Access mode: Read-only

Niche connector. This system is queryable via Flume’s Lakehouse (Trino) and supported on request. It is not part of the standard data estate onboarding but is available for clients with specific requirements.

Required information

FieldDetails
Prometheus endpointPrometheus server URL or Thanos Query endpoint. Grafana Cloud: provided endpoint.
PortDefault 9090. Grafana Cloud: HTTPS on 443.
AuthenticationVaries: no auth (internal), basic auth, bearer token, or OAuth (Grafana Cloud).
Metric scopeMetric names or label selectors to scope access.

Network considerations

Self-managed: VPN or direct access to port 9090. Prometheus is often internal-only.

Grafana Cloud: HTTPS over 443. API key authentication.

Thanos: Query component endpoint, typically on port 9090 or custom.

Amazon Managed Prometheus: AWS SigV4 auth over HTTPS. VPC endpoint available.

Trino access: Flume’s Lakehouse queries Prometheus via the Trino Prometheus connector through the HTTP API.

Credential and auth management

Self-managed: Often no auth when behind VPN. If auth enabled, basic auth or reverse proxy with auth layer.

Grafana Cloud: API key with MetricsViewer role.

Amazon Managed Prometheus: IAM role with aps:QueryMetrics permission.

Validation checks

CheckMethodExpected result
Network reachabilitycurl http://<host>:9090/-/healthyReturns Prometheus Server is Healthy.
Query testcurl 'http://<host>:9090/api/v1/query?query=up'Returns metric data
Label listingGET /api/v1/labelsLists available labels
Trino querySELECT * FROM prometheus.<metric> LIMIT 1 via TrinoReturns metric data points

Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.