Iterative metrics, dashboards and monitors
summary
Shows how Atlassian moves dashboards and monitors into code, using Splunk XML export/import, webhooks and a small service called Sauron to auto-sync changes and surface all dashboards for incidents. Evidence: a 91‑owner survey found 83.5% still edit via UI, 67% rely on tribal knowledge, and one product had 286 dashboards for JIRA. Weekly tech ops reviews cut noisy alerts over 21 weeks and produced actionable monitors and templates that scale across shards.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:10Iterative metrics, dashboards & monitors
- 17:23What questions do you want to answer?
- 19:49What level of service you can commit to offer
- 29:49Operational resources as code
- 30:59286 Dashboards
- 34:5850 Services adopted Sauron
related talks
21mChallenges, Best Practices, and Solutions for Monitoring and Alerting...
14mWhat dashboards don't tell you
52mBuilding a culture of observability
21mDashboards and Runbooks: Scrapbooking for Engineers
23mDashboards for DevOps: How to Set Up the Right Reports
21mJourney from Broken Dashboards to O11y Maturity
31mService cockpit - developer friendly Grafana based monitoring aggregator
46mUsing OpenTelemetry, Splunk, and CI(Jenkins) to deliver a Monitoring Solution for Financi...