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

Beelines and OpenTelemetry

Honeycomb’s data ingest path supports several different types of instrumentation, including two approaches specific to instrumenting code: Honeycomb’s Beelines and vendor-neutral OpenTelemetry. Both of these approaches generate the structured event data format that will help you get the most out of Honeycomb.

New to instrumenting code? Want to learn about structured events? Read more about instrumentation.

Beelines vs. OpenTelemetry  🔗

When Should I Use Beelines?  🔗

When Should I Use OpenTelemetry?  🔗

Neither Secure Tenancy nor Refinery currently support OTLP ingest. To use them with OpenTelemetry instrumentation, you must run a Honeycomb Exporter to export Honeycomb JSON data.

Paths to Getting Data into Honeycomb

What is the Honeycomb Roadmap?  🔗

As OpenTelemetry grows to embrace more languages, Honeycomb plans to continue to support OpenTelemetry; we see OpenTelemetry as a key component of our ability to support many different programming languages and environments.

Tracing Interoperability  🔗

You don’t need to instrument all the services in your stack the same way. If one service is instrumented with OpenTelemetry and another with Beelines, you can still get trace visualizations that include them both! In order to do that, the Beelines include marshal and unmarshal functions that can generate and parse W3C Trace Context headers, the format used by OpenTelemetry.

To learn more about ongoing development for W3C trace context propagation, visit the W3C Trace Context GitHub repository.