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

Open standards

OpenTracing and OpenCensus are two popular vendor-neutral open standards for adding distributed tracing instrumentation to your systems. These projects have been superseded by the OpenTelemetry standard. Honeycomb can ingest data from both OpenTracing and OpenCensus, and supports OpenTelemetry via the Collector as well as language-specific SDKs/exporters.

Note: For most teams, Honeycomb’s Beelines are the fastest, most direct route to rich instrumentation — but we know for teams with existing instrumentation, consistency across your codebases may be more important than reducing instrumentation work. If you already use OpenCensus, OpenTracing, or OpenTelemetry in your applications, you may want to use these standards to send your data to Honeycomb too.

OpenTelemetry  🔗

OpenTelemetry is a new project that will be the successor to OpenCensus and OpenTracing. The OpenTelemetry project is currently in beta.

Honeycomb has an exporter in the OpenTelemetry collector contrib binary, so you should be able to configure the Collector regardless of which language you are using.

Honeycomb provides a variety of Exporters to send OpenTelemetry traces to Honeycomb from any OpenTelemetry instrumented applications. The following exporters are currently available:

OpenCensus  🔗

Honeycomb provides the Honeycomb OpenCensus Go Exporter to send OpenCensus traces to Honeycomb from go applications. See our Sending Trace Data docs for more information on how to send us data using the Exporter.

If you have a Python or Elixir application instrumented with OpenCensus, check out our community-created Python Exporter or Elixir Exporter.

Our Exporters also work with OpenCensus Service, which allows OpenCensus-instrumented apps to easily export data to multiple backends. The flexibility of the OpenCensus Agent also means that the Agent can be used to capture OpenCensus data from languages without an official Honeycomb exporter, and forward them on to Honeycomb’s servers.

OpenTracing  🔗

Honeycomb can work with OpenTracing data in the Zipkin wire format, one of the common ways to send OpenTracing data to a tracing backend. To send this data to Honeycomb, you’ll need to run a simple proxy that will forward this data from your Zipkin-instrumented app to the Honeycomb backend. See our Sending Trace Data docs for more information on how to run the proxy and send us OpenTracing data.