Javascript is a pretty prolific programming language, used daily by people visiting any number of websites and web applications. NodeJS, it’s server-side version, is also used all over the place. You’ll find it deployed as full application stacks to functions in things like AWS Lambda, or even as IoT processes with things like Johnny Five. So when we think about Observability in the context of a nodejs stack, how do we set it up and get the information flowing?

Microservices and distributed architectures have become the norm for building modern day applications. While the cloud has made it easier to deploy and scale microservices, it has opened up a complex set of problems for DevOps by virtue of the sheer volume of interactions between those services.

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 enough of a familiarity with the discipline to get myself into trouble, 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.

At Honeycomb, we talk a lot about eating our own dogfood. Since we use Honeycomb to observe Honeycomb, we have many opportunities to try out UX changes ourselves before rolling them out to all of our users. UX doesn’t stop at the UI though! Developer experience matters too, especially when getting started with observability. We often get questions about the difference between using our Beeline SDKs compared with other integrations, especially OpenTelemetry (abbreviated “OTel”).

It’s that time of year again — the DevOps Pulse 2020 is here! Last year, nearly 1,000 engineers around the world provided their insights in the DevOps Pulse 2019 so we could get the community’s perspective on the growth and challenges associated with observability, cloud monitoring and more. As we discovered in last year’s DevOps Pulse, observability is still a major challenge for many organizations.

I have been noticing that a lot of folks are often confused between event logging and tracing. In terms of building out a generic SD for devs to report on observability data, should Event APIs be distinct from Trace APIs? Is an Event just a single Trace Span ? If you look at Honeycomb’s implementation, an Event seems to be equivalent to a single span trace. The middleware wrapper creates a Honeycomb event in the request context as a span in the overall trace.

A fireside chat to discuss use cases and deployment tips for AIOps with observability generated a stream of compelling questions from attendees, which the Moogsoft hosts answered with depth and expertise. Combining AIOps analysis with detailed observability data is key for DevOps and SRE teams to attain continuous service assurance, so Moogsoft just published a new ebook about this topic titled “Observability with AIOps For Dummies.”