We use cookies or similar technologies to personalize your online experience & tailor marketing to you. Many of our product features require cookies to function properly.

Read our privacy policy I accept cookies from this site

Prometheus Clients Beta

If you have a system that’s instrumented as a Prometheus client, you can use OpenTelemetry Collector to scrape metrics data from that client’s endpoint and send it to a Honeycomb dataset.

How It Works  🔗

Prometheus is a widely adopted open source metrics server with its own API and client libraries. Prometheus clients expose their metrics on an HTTP endpoint. Prometheus servers can then connect to that endpoint and store the metrics they provide. OpenTelemetry Collector acts like a Prometheus server, and will transform Prometheus metrics signals into OpenTelemetry Metrics signals, which can then be forwarded to Honeycomb over the OpenTelemetry Line Protocol (OTLP).

An architecture diagram depicting an instrumented app exposing a Prometheus endpoint, which is being scraped by OpenTelemetry Collector. OpenTelemetry Collector is then sending data to Honeycomb over OTLP.

Instrumenting Your Application as a Prometheus Client  🔗

Refer to the Prometheus documentation to find details about the appropriate client library for your application.

Installing and running OpenTelemetry Collector  🔗

Find and download a recent release of OpenTelemetry Collector from the Releases page on GitHub.

OpenTelemetry Collector requires a configuration file to run (find more details below). If your configuration file exists in the current working directory at otel_collector_config.yaml, you can then run it using the following command:

otel-collector --config $(pwd)/otel_collector_config.yaml

See more about using OpenTelemetry Collector with Honeycomb.

Configuring OpenTelemetry Collector  🔗

To scrape Prometheus endpoints, you’ll need to configure OpenTelemetry Collector with a pipeline that starts with a prometheus receiver. To forward scraped metrics to Honeycomb, your pipeline should end with an otlp exporter. Pipelines are specified in an OpenTelemetry Collector configuration file. Here’s a barebones example of a configuration file configured to scrape prometheus metrics and send them to Honeycomb:

        - job_name: "prometheus"
          scrape_interval: 15s
            - targets: [""] # this is the endpoint to scrape

    endpoint: "api.honeycomb.io:443"
      "x-honeycomb-team": "YOUR_API_KEY"
      "x-honeycomb-dataset": "DESTINATION_DATASET_NAME"

      receivers: [prometheus]
      processors: []
      exporters: [otlp/metrics]