With Honeycomb, the engineering team at IMO was able to find hidden architectural issues that were previously obscured in their logs, generating new insights that unlocked reliability and efficiency gains.

You can & should send metrics to Honeycomb! But you'll likely replace 95% of those with structured events. How does that work?

Customer Success Engineer Emily Ashley describes her experience listening to the o11ycast backlog as part of her onboarding, and why the podcast is a great resource for anyone new to observability.

As a Customer Advocate, I talk to a lot of prospective Honeycomb users who want to understand how observability fits into their existing Site Reliability Engineering (SRE) practice. While I have a passing familiarity with the discipline, I wanted to learn more about what SREs do in their day-to-day work so that I’d be better able to help them determine if Honeycomb is a good fit for their needs.

We often get questions about the difference between using our Beeline SDKs compared with other integrations, especially OpenTelemetry (abbreviated "OTel"). That’s why the team decided to do some integration dogfooding by instrumenting our own code with OpenTelemetry alongside existing Beeline instrumentation.

Every once in a while, teams or systems hit an inflection point where enough things change at once and the pattern of incidents shifts. We found ourselves at an inflection point like that last week.

Have you heard the buzz about observability with Honeycomb 🐝? It’s the best tool on the market for observing your systems in real time to reduce toil and delight users. But don’t listen to us, listen to our kickass community of “Pollinators”--this blog post is dedicated to them 💖