Q & A
summary
Split persistent displays into two concrete types: triage dashboards that surface a very small set of dive-into metrics for fast incident response and business/executive dashboards that show many status indicators tied to revenue or SLAs. Communicate feature requests with clear expected response windows instead of vague promises, use empathy when saying no, record decisions about alert thresholds, designate a tie breaker for disputes, and agree on criteria for when thresholds change. Mentions include PagerDuty practices and a Slack regex feature request example.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:26Remote information radiators
- 3:56Prioritizing requests empathetically
- 8:09Alert noise level thresholds
- 10:53Closing remarks
related talks
43mObserving from Incidents
21mLive Q&A Session #1
14mWhat dashboards don't tell you
30mDevEx and Productivity Metrics on Backstage - Do's and Don'ts
35mIncident Management: Lessons from Emergency Services
44mIterative metrics, dashboards and monitors
45mIncident Management - Talk the Talk, Walk the Walk
19mSensory Friendly Monitoring