Prometheus Scrape via OTel (Guided)

This package allows you to scrape Prometheus-compatible metrics endpoints using the OpenTelemetry Collector's Prometheus receiver.

This package configures the Prometheus receiver in the EDOT collector to scrape metrics from Prometheus-compatible endpoints. The Elastic Agent processes and enriches the data before sending it to Elasticsearch for indexing and analysis.

Configure individual fields like targets, scrape interval, and TLS settings through the Fleet UI.

Looking for raw config mode? If you have an existing Prometheus scrape_configs YAML that you want to use directly, consider using the Prometheus Scrape via OTel (Custom Config) package instead.

For HTTPS endpoints, you can configure:

• Skip TLS verification for self-signed certificates
• CA certificate path for custom certificate authorities
• Client certificate and key for mutual TLS authentication

Configure either basic authentication or a Bearer token — not both.

Set Username and Password for endpoints that require HTTP basic authentication.

Set Bearer Token for endpoints that require Authorization: Bearer <token> (for example, Temporal Cloud OpenMetrics).

If both Username and Bearer Token are set, the package configures basic authentication only and ignores the Bearer Token. Clear Username (and Password) when you intend to use Bearer authentication.

Some Prometheus-compatible endpoints accept query parameters to filter or scope the metrics they return (for example, Temporal Cloud's namespaces and labels parameters). Use the Query Parameters field — do not append them to Metrics Path.

The Prometheus receiver places metrics_path verbatim into url.URL.Path, and Go's net/url percent-encodes ? in path context (%3F), producing a request the server does not recognise. The params map is placed into url.RawQuery instead, which preserves the ? delimiter.

Example:

namespaces:
  - my-namespace.account
labels:
  - temporal_activity_type
		

For detailed configuration options and their descriptions, refer to the Prometheus Receiver documentation in the upstream OpenTelemetry Collector repository.

• Monitor applications exposing Prometheus metrics
• Scrape Node Exporter, cAdvisor, or other Prometheus exporters
• Collect custom application metrics in Prometheus format
• Migrate from Prometheus to Elastic Observability

This package requires:

• Kibana 9.2.0 or later
• Elastic Agent with OpenTelemetry Collector support