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

How It Works 

OpenTelemetry SDKs are implemented and stable for several languages. They provide an API, which allows your application to create custom metrics with metrics instruments like counters, histograms, and gauges. Instrumentation libraries used in different languages can also capture metrics from the application’s runtime environment, such as the number of HTTP requests served by an HTTP server. OpenTelemetry SDKs can then be configured to send metrics to Honeycomb over OpenTelemetry 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 will need to enable an OTLP exporter and it should have:

  • a destination of api.honeycomb.io:443
  • 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

Troubleshooting Metrics 

Metrics Sent to unknown_metrics 

If using Honeycomb and a metrics dataset is not specified, all metrics data will be sent to a dataset called unknown_metrics. Once you specify a metrics dataset, all metrics data will be sent to that dataset.

This troubleshooting scenario is not applicable to Honeycomb Classic users.

Did you find what you were looking for?