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.
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).
Refer to the Prometheus documentation to find details about the appropriate client library for your application.
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
To scrape Prometheus endpoints, you’ll need to configure OpenTelemetry Collector with a pipeline that starts with a
To forward scraped metrics to Honeycomb, your pipeline should end with an
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:
receivers: prometheus: config: scrape_configs: - job_name: "prometheus" scrape_interval: 15s static_configs: - targets: ["0.0.0.0:9100"] # this is the endpoint to scrape exporters: otlp/metrics: endpoint: "api.honeycomb.io:443" headers: "x-honeycomb-team": "YOUR_API_KEY" "x-honeycomb-dataset": "DESTINATION_DATASET_NAME" service: pipelines: metrics: receivers: [prometheus] processors:  exporters: [otlp/metrics]