I always tell people "Observability is not logs, metrics, and traces! Observability is empowering your team to ask questions." That's very aspirational and sounds good, but it's not at all clear. I now have a self-contained story that perfectly explains it!
Being on call is challenging. It’s signing up to be operating complex services in a totally interruptible manner, at all hours of the day or night, with limited context. It’s therefore critical to have proper on-call on-boarding procedures, offer continuous training sessions, and continuously improve documentation. We also need to make sure people feel safe by providing ways to reduce their stress, and make room for questions to surface all sorts of uncertainties around our operations.
Big news: I can finally stop pointing anyone who asks about Honeycomb’s story for frontend observability to Emily’s blog post from 2017 on “Instrumenting Page Loads with Honeycomb.” (It was a great post, don’t get me wrong, but I don’t think any of us knew it would bear such weight for so long.) I am ecstatic to announce that we have released a new whitepaper called “Getting Started With Honeycomb Client-Side Instrumentation for Browser Applications,” wri
The Game Developers Conference (GDC) is a yearly event that brings together leading brands in the gaming industry to talk about trends in development and showcase new features and releases. One of the cool things about the conference is that it’s an excellent opportunity for gaming enthusiasts, aspiring game developers, and industry vendors to connect, network, learn and celebrate the achievements of the industry.
Dear Acronymically, I'll try to answer without using a single (new) acronym! First things first—"PRO" refers to our Pro plan, rather than being an acronym in and of itself. Honeycomb Pro is our cost-effective offering for professionals like you who are running a few production workloads! And we're hoping that folks will get even more benefit now that they have access to our SLO feature!
Honeycomb Pro is about to get even better. Starting today, all Pro accounts have access to Honeycomb Metrics and two Service Level Objectives (SLOs), previously only available to Enterprise accounts. Full disclosure: Later this month, the price of Pro plans will be increasing as well (see below). However, existing Pro customers (including those that sign up before the new pricing goes into effect) will be able to enjoy the new capabilities at existing prices for a full year, until April 2023!
We’ve made some big changes under the hood at Honeycomb to give you better control over how you put your apps data to work—we’ve expanded our core data model with formal Environments and Services! In short, the best observability (o11y) platform in town just got better! Before we dig in, an important note. Existing Honeycomb teams are not impacted by this update. If you’re already a Honeycomb user, congratulations! Your team is now a Honeycomb Classic team.
Observability came out of microservices and cloud-native, right? If you have a simpler architecture, does o11y matter?” — this question came up during recent office hours Yeah, sort of. On both counts—yeah, it sorta came out of microservices and cloud native, and yeah sorta, you need it with a simpler architecture (though perhaps not as desperately as you otherwise might).
Today, the Honeycomb OpenTelemetry Distribution for Java reaches a major milestone with a 1.0 release. This is the first Honeycomb OTel Distro to come out of beta and go into the general release category, and you can expect more to come!
TL;DR: startSpan is easier and measures a duration. Use it if your work won’t create any subspans. startActiveSpan requires that you pass a callback for the work in the span, and then any spans created during that work will be children of this active span. I’m instrumenting a Node.js app with OpenTelemetry, and adding some custom instrumentation. For this important activity that I’m doing (let’s call it “retrieve number”), I’m creating a custom span.
