This feature is available as part of the Honeycomb Enterprise and Pro plans.
The OpenTelemetry Metrics API is in “feature-freeze” status, targeting completion in the first half of 2022. As a result, all OpenTelemetry Metrics SDKs may still be subject to breaking changes. If you prefer stability, 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.
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).
Refer to the OpenTelemetry SDK Documentation for your environment for details on how to instrument your application. You will need to enable an OTLP (OpenTelemetry Line Protocol) exporter and it should have:
x-honeycomb-teamheader with an API key that has write permissions
x-honeycomb-datasetheader with the name of the dataset you would like to send metrics to
If using Honeycomb and a metrics dataset is not specified, all metrics data will be sent to a dataset called
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?