Application Metrics with the OpenTelemetry SDKs | Honeycomb

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

Application Metrics with the OpenTelemetry SDKs

This feature is available as part of the Honeycomb Enterprise plan.

The OpenTelemetry Metrics API is in “draft” status, targeting completion in the second half of 2021. As a result, all OpenTelemetry Metrics SDKs are still subject to breaking changes. Until then, for production applications, we recommend instrumenting your application with a Prometheus client library and using OpenTelemetry Collector to scrape those metrics and send them to Honeycomb. Learn more about receiving metrics from Prometheus.

How It Works  🔗

OpenTelemetry SDKs have been implemented for various languages. They can collect a standard set of runtime metrics (for instance, information about memory usage, garbage collection, or parallelization). In some cases, they also instrument commonly used frameworks and libraries. They also provide an API allowing your application to custom metrics. OpenTelemetry SDKs can then be configured to send metrics to Honeycomb over OpenTelemetry Line Protocol (OTLP).

An architecture diagram depicting an application instrumented with OpenTelemetry SDK, which is sending data to Honeycomb over OTLP.

Instrumenting Your Application  🔗

Refer to the OpenTelemetry SDK Documentation for your environment for details on how to instrument your application. You’ll need to enable an OTLP (OpenTelemetry Line Protocol) exporter and it should have:

  • a destination of
  • an x-honeycomb-team header with an API key that has write permissions
  • an x-honeycomb-dataset header with the name of the dataset you would like to send metrics to