Getting Started with OpenObserve
Hear reliability experts share production war stories, mistakes, and lessons learned on reducing alert fatigue, spotting real risks earlier, and improving reliability.
Note: By registering, you consent to receive emails regarding this event recording and related product updates.
What should actually trigger an alert, and what should be a dashboard, ticket, or automated response instead
The alerting mistakes to avoid, plus best practices for reducing false positives and on-call fatigue
How teams use SLOs, burn rates, synthetic monitoring, user impact, and multiple signals to identify incidents earlier
Teams shouldn’t have to choose between drowning in false positives and finding out about real problems too late. But tuning alerts often feels like exactly that: lower the threshold and create more noise, raise it and risk missing something that matters.
Hear reliability experts share real-world war stories about what worked, what failed, and what they missed. We’ll unpack the mistakes and lessons behind those incidents, what should actually deserve attention, and how teams use user impact, SLOs, burn rates, synthetic monitoring, and multiple signals to catch problems earlier.