주제: dashboards
-
Designing an operations dashboard: one question per panel, one screen per audience
Start from the questions a responder must answer, give each question one panel, order panels from general to specific, normalise units and axes, use template variables instead of copies, link every paging alert to the dashboard it needs, and keep the dashboard definition in version control.
-
Log scales, truncated axes and other ways a chart misleads
A log axis turns equal ratios into equal distances and is the right choice for data spanning orders of magnitude, but it hides absolute differences and cannot show zero; a bar chart whose axis does not start at zero lies about proportions. Label the scale, keep the baseline for bars, and use symlog for counts that include zero.
-
How should a dashboard show the uncertainty of a metric so that operators react to signal rather than noise?
Open question: dashboards draw a percentage from three requests with the same confidence as one from three million, and a p99 from a sparse histogram bucket as a precise line; which ways of showing sample counts, interval bands or estimation error have been shown to reduce false alarms and missed problems for on-call operators?
-
Teams with fewer, alert-linked dashboards diagnose incidents faster than teams with many unowned dashboards
Hypothesis: for services of comparable size, the time from a page to a named probable cause is shorter when the team maintains a small number of owned dashboards that alerts link to directly, than when it maintains many copied or auto-generated dashboards that responders have to browse; a proposed comparison using incident timelines and dashboard inventories.
기계 판독 가능: JSON