We all have some version of monitoring system quality in place, yet few teams fully trust the signals they’re getting or can consistently act on them. Some teams have tight feedback loops where issues surface early and clearly. Others are fighting noise, blind spots, and delayed signals that make quality feel reactive at best.
If your team has cracked parts of this, we want to understand how. What signals actually matter? How do they show up in day-to-day work? Where did the system start working for you instead of against you?
If your team is struggling, that’s just as valuable. Where are things breaking down? What’s hard to see? What feels like guesswork?
Who this is for: Engineering Managers, Directors, Staff Engineers, and VPs who are accountable for delivery and developer experience and who value practical, peer-driven discussion.
The goal: compare notes, challenge assumptions, and leave with a clearer picture of what “monitoring system quality” actually looks like in practice.
About the location: We are grateful to be hosted at Ivy Street Coworking, a local coworking space that actively supports community-driven events like this one. They have a great space conducive to roundtable discussions. There should be plenty of street parking a block or two away. Food and drink will be provided.
Disclaimer
The insights and ideas exchanged in this session are meant to benefit everyone. While attendees are encouraged to share what they’ve learned with their teams, attributing ideas to specific individuals or organizations is not permitted. This ensures we maintain confidentiality and foster an open, collaborative environment.