Operations | Monitoring | ITSM | DevOps | Cloud

I have a performance problem with my web application. This video shows how I use Honeycomb's Frontend Observability Web Launchpad to quickly identify the symptoms causing the slowdown.

Honeycomb Service Level Objectives (SLO) can notify your team when one of your error budgets are being exhausted. See how the SLO view gets you from zero information to identification in one click!

As a software developer, how is observability relevant to me? What is this OpenTelemetry thing? Austin Parker gives a great overview.

Charity breaks down the progress in Observability in recent years: there's a sea change underway. This is not an incremental improvement, but a radical shift in how we understand the software we build.

Charity Majors brought the word "observability" into software. Now she describes the one major shift that we need to get more out of observability at lower cost.

What do you do when OpenTelemetry is sending way more telemetry than you expect? Jessitron walks you through 2 quick ways to check where all that data is coming from.

In this 3-minute preview of our Director's Guide to Observability.

Liz Fong-Jones walks you through how we debugged our Kubernetes Autoscaler with Honeycomb Log Analytics to achieve cost savings with Graviton4 instances. Having great observability is one way Honeycomb saves money.

In this installment of Ask the Experts, Anijah asks Zach McCoy about distributed and what problems it solves.

When an alert goes off because a Service Level Objective (SLO) is in danger of violation, it comes with a lot of context about what has been going wrong and for how long. Then Honeycomb gives you tools to explore the where & why. Here, Martin Thwaites walks through an example of diagnosing slower performance. What service is the problem, and under what circumstances?