Operations | Monitoring | ITSM | DevOps | Cloud

Apdex in Honeycomb

“How is my app performing?” is one of the most common, yet hardest questions to answer. There are myriad ways to measure this, like error rate, average response time, and so on. Enter the Application Performance Index (aka Apdex), a single metric that attempts to answer, “Are my application’s users happy?” Apdex is an open standard that was formalized in 2005 by the Apdex Alliance.

See Your Structured Logs in the Explore Data tab

There's a new way to flip through your data in Honeycomb, released this week! It's super for looking at structured logs. It's called: Explore Data. Get directly at the logs, spans, events, or metrics that power the fast analysis you can do with Honeycomb. See all the fields, the whole variety of values — now ordered by timestamp, with pagination. Modify your query and graphs right from the data table. It's all connected!

Making Room for Some Lint

It’s one of my strongly held beliefs that errors are constructed, not discovered. However we frame an incident’s causes, contributing factors, and context ends up influencing the shape of the corrective items (if any) that get created. I’ll cover these ideas by using our June 3rd incident where a database migration caused a large outage by locking up a shared database and making it run out of connections.

The CoPE and Other Teams, Part 1: Introduction & Auto-Instrumentation

The CoPE is made to affect, meaning change, how things work. The disruption it produces is a feature, not a bug. That disruption pushes things away from a locally optimal, comfortable state that generates diminishing returns. It sets things on a course of exploration to find new terrains which may benefit it more—and for longer.

Destroy on Friday: The Big Day A Chaos Engineering Experiment - Part 2

In my last blog post, I explained why we decided to destroy one third of our infrastructure in production just to see what would happen. This is part two, where I go over the big day. How did our chaos engineering experiment go? Find out below!

What Makes for a 'Good' Pair Programming Session?

Software changes so rapidly that developing on the cutting edge of it cannot fall to a single person. When it comes to asynchronously disseminating information about projects, code comments, PR conversations, Slack, RFCs, and other investigatory documents do a wonderful job, but no amount of async communication replaces the magic of two brains bouncing ideas off of each other.

Deploy on Friday? How About Destroy on Friday! A Chaos Engineering Experiment - Part 1

We recently took a daring step to test and improve the reliability of the Honeycomb service: we abruptly destroyed one third of the infrastructure in our production environment using AWS’s Fault Injection Service. You might be wondering why the heck we did something so drastic. In this post, we’ll go over why we did it and how we made sure that it wouldn’t impact our service.

Optimizing Database Performance with Honeycomb Relational Fields

Martin investigates: what database queries are taking the longest? Then he digs into the one taking the most time, and asks: What user-initiated requests trigger this query? This kind of question helps developers focus our efforts where they count. And it's possible in Honeycomb with Relational Fields. This is #observability during development, using #OpenTelemetry #tracing and Honeycomb.