--- title: Prometheus Scrape via OTel (Guided) description: This package allows you to scrape Prometheus-compatible metrics endpoints using the OpenTelemetry Collector's Prometheus receiver. This package configures... url: https://www.elastic.co/docs/reference/integrations/prometheus_input_otel products: - Elastic integrations applies_to: - Serverless Observability projects: Preview - Serverless Security projects: Preview - Elastic Stack: Preview since 9.2 --- # Prometheus Scrape via OTel (Guided) | | | |-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| | **Version** | 0.3.0 : Preview ([View all](#changelog)) | | **Subscription level**[What's this?](https://www.elastic.co/subscriptions) | Basic | | **Developed by**[What's this?](https://www.elastic.co/docs/reference/integrations/developed-by) | Elastic | | **Minimum Kibana version(s)** | 9.2.0 | To use pre-release integrations, go to the **Integrations** page in Kibana, scroll down, and toggle on the _Display beta integrations_ option. ## Overview This package allows you to scrape Prometheus-compatible metrics endpoints using the OpenTelemetry Collector's [Prometheus receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/prometheusreceiver). ### How it works 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. ## Configuration 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)](https://github.com/elastic/integrations/tree/main/packages/prometheus_input_otel_raw) package instead. ### Settings | Setting | Description | Default | |------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| | Scrape Targets | List of targets in `host:port` format | `localhost:9090` | | Scrape Interval | How frequently to scrape targets | `60s` | | Scrape Timeout | Timeout for scraping | `10s` | | Metrics Path | HTTP resource path to fetch metrics. **Path only** — do not append query parameters here; use Query Parameters instead. | `/metrics` | | Query Parameters | Prometheus scrape query parameters as a YAML map of parameter name to list of values. These are appended to the scrape URL as a proper query string. | — | | Scheme | Protocol scheme (HTTP/HTTPS) | `http` | | Honor Labels | Honor labels from scraped metrics | `false` | | Honor Timestamps | Honor timestamps from scraped metrics | `true` | | Username | Username for HTTP basic authentication | — | | Password | Password for HTTP basic authentication (use with Username) | — | | Bearer Token | Token sent as `Authorization: Bearer ` | — | ### TLS Configuration 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 ### Authentication Configure **either** basic authentication **or** a Bearer token — not both. #### Basic Authentication Set **Username** and **Password** for endpoints that require HTTP basic authentication. #### Bearer Token Authentication Set **Bearer Token** for endpoints that require `Authorization: Bearer ` (for example, Temporal Cloud OpenMetrics). #### Mutual exclusivity 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. ### Query Parameters 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:** ```yaml namespaces: - my-namespace.account labels: - temporal_activity_type ``` ## Configuration Reference For detailed configuration options and their descriptions, refer to the [Prometheus Receiver documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/prometheusreceiver/README.md) in the upstream OpenTelemetry Collector repository. ## Use Cases - 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 ## Compatibility This package requires: - Kibana 9.2.0 or later - Elastic Agent with OpenTelemetry Collector support ## Changelog | Version | Details | Minimum Kibana version | |-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| | **0.3.0** | **Bug fix** ([View pull request](https://github.com/elastic/integrations/pull/21564))Add `params` variable to pass Prometheus scrape query parameters separately from the metrics path, preventing percent-encoding of '?' in the URL path. | 9.2.0 | | **0.2.0** | **Enhancement** ([View pull request](https://github.com/elastic/integrations/pull/20695))Add Bearer token authentication support for scrape targets. | 9.2.0 | | **0.1.2** | **Enhancement** ([View pull request](https://github.com/elastic/integrations/pull/20546))Add group field to package manifest. | 9.2.0 | | **0.1.1** | **Enhancement** ([View pull request](https://github.com/elastic/integrations/pull/19526))Update package title and description to improve clarity of use. | 9.2.0 | | **0.1.0** | **Enhancement** ([View pull request](https://github.com/elastic/integrations/pull/17117))Initial release of the Prometheus OpenTelemetry Input package with guided configuration | 9.2.0 |