Using OpenTelemetry With Honeycomb
Instrumenting your apps to emit telemetry is a foundational requirement for observability. But that instrumentation can present an immediate barrier to entry if your particular language or framework isn’t supported, or if you’ve already invested time to adopt one vendor’s telemetry libraries and decide you want to try a different solution. You shouldn’t be locked into using specific vendor tools for something as fundamental as code instrumentation. OpenTelemetry (or OTel) is an open-source project that provides tools, APIs, and SDKs that let you instrument your applications once and send your telemetry data to any tool of your choice. At Honeycomb, we believe the value you get from observability isn’t about the data itself, it’s about your ability to analyze that data effectively. We actively contribute to and support the OpenTelemetry project because we believe instrumentation should be table stakes, easy, and so commonplace that it’s almost boring. In order to get there, we must build for a future where OpenTelemetry is the de facto standard for instrumentation. In this webinar, you’ll learn: - What OpenTelemetry is, how it makes instrumenting your code easier, and why it should be a key part of your observability strategy - The various ways you can use OpenTelemetry with Honeycomb - How Honeycomb OTel Distros can jumpstart your instrumentation experience - What to expect from Honeycomb and OpenTelemetry going forward
Instrumentation Options Designed For Success
Instrumenting your code is the first step toward observability. The telemetry data emitted by your applications and systems will help you debug any number of complex issues in the future. Instrumenting the right telemetry is critical for developers, SREs, and DevOps teams that own operation of their services in production. Honeycomb helps you ensure your team has the right telemetry when you need it the most.
Honeycomb & OpenTelemetry: Instrumentation Should Be Boring
OpenTelemetry is a collection of tools, APIs, and SDKs that can be used to instrument, generate, collect and export telemetry data for analysis in order to understand your software’s performance and behavior. Paul gives an overview of how Honeycomb has embraced OpenTelemetry as a key part of our instrumentation strategy, how this can help make instrumenting your code easier, and what you can expect from Honeycomb and OpenTelemetry in the near future.