Prometheus

Collect Prometheus Metrics with OpenTelemetry Collector

The OpenTelemetry Collector can be configured to scrape Prometheus metrics, effectively acting as a drop-in replacement for the Prometheus server. This integration allows for a seamless transition from Prometheus to OpenTelemetry, enabling users to leverage both systems' strengths.

Key Components

• Prometheus Receiver: This component in the OpenTelemetry Collector is designed to scrape metrics from Prometheus targets. It supports the full set of Prometheus scraping configurations, including service discovery and relabeling.
• Target Allocator: An optional component introduced by the OpenTelemetry Operator to simplify Prometheus receiver configuration. It ensures even distribution of Prometheus targets among multiple Collector instances and facilitates the discovery of Prometheus Custom Resources.

Advantages

• Flexibility: Allows gradual migration from Prometheus to OpenTelemetry.
• Scalability: With the Target Allocator, it's possible to distribute scraping load across multiple Collector instances.
• Interoperability: Enables the use of Prometheus metrics within the OpenTelemetry ecosystem and Dash0.

Overview

Many Kubernetes services and pods expose metrics through a Prometheus endpoint that you can scrape. We recommend to scrape and forward these metrics via an OpenTelemetry Collector.

Prometheus metrics endpoint

To make your services scrapeable, add these annotations to your pod or service definitions

Collector Configuration

The following code snippet shows an OpenTelemetry Collector configuration file.

Collector Deployment

Learn how to deploy the collector within our OpenTelemetry collector integration documentation.

References

• OpenTelemetry Collector configuration in OTelBin