Incident Response Using Triggered SLOs
Watch our fireside chat with Honeycomb’s Principal Developer Advocate Liz Fong-Jones, Solution Architects Director Pierre Tessier, and SRE Fred Hebert, where Fred shows how he used a service-level objective (SLO) to understand and fix a recent incident. They discuss the value of being alerted on the right SLOs and how we were able to take action quickly. Listen in to learn how you can: - Set up for success by adding the right context to data through wide events - How to pair with meaningful, debuggable SLOs so you can sleep better at night
Debuggable Service Level Objectives
Honeycomb’s Service Level Objectives (SLOs) offer more actionable alerts with less noise. They’re also integrated right into your debugging workflows.
Honeycomb Service Level Objectives (SLOs)
In this three minute video, you’ll see how Honeycomb’s actionable SLOs can help you get to the source of an issue faster. Using a real production SLO (latency per-event) as an example, we walk you through what exhaustion time alerts are and how to configure them, as well as how to use a heatmap to investigate and take action when things happen.
Reliable Alerting for Honeycomb Triggers and SLOs With PagerDuty
Now that your SLOs are running, how does the team know when critical systems are in trouble? Join Developer Advocates Mandi Walls at PagerDuty and Liz Fong-Jones at Honeycomb for a demo on how PagerDuty can notify on-call responders based on alerts sent from Honeycomb.