Register for the webinar and download the full study to see and apply Forrester’s financial model to determine the observability ROI for your organization. Many teams want to adopt observability and Honeycomb—but run into budget roadblocks because budget holders may not clearly understand the quantifiable benefits to their end users, their teams, and the bottom line.

OpenTelemetry (or “OTel”) helps you get your instrumentation started quickly, and it helps you get the most out of that telemetry data by providing flexible exporting options. As a result, it’s emerging as the new standard for instrumentation. To that end, today we’re sharing more insight into the work we’ve done (and are doing) to enable a path for all Honeycomb users toward OTel adoption. We hope you’ll be as excited as we are to embrace these open standards!

Honeycomb is known for its incredibly fast performance: you can sift through billions of rows, comparing high-cardinality data across thousands of fields, and get fast answers to your queries. And none of that is possible without our purpose-built distributed column store. This post is an introduction to what a distributed column store is, how it functions, and why a distributed column store is a fundamental requirement for achieving observability.

Your feedback is what makes Honeycomb better. We ship changes often (you can see updates in real time on our changelog), so it can be easy to miss some of the new improvements that can help you get the most out of Honeycomb. Whether it’s a big new product feature or an enhancement of existing features, you may not always be up on the latest goodness waiting for you in Honeycomb.