Cited by 56Software System Performance and ReliabilitySoftware Engineering ResearchSoftware Engineering Techniques and Practices

How to mitigate the incident? An effective troubleshooting guide recommendation technique for online service systems

Jiang, Jiajun, Lu, Weihai, Chen, Junjie, Lin, Qingwei, Zhao, Pu, Kang, Yu, Zhang, Hongyu, Xiong, Yingfei +4 more·2020·Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering

Abstract

In recent years, more and more traditional shrink-wrapped software is provided as 7x24 online services. Incidents (events that lead to service disruptions or outages) could affect service availability and cause great financial loss. Therefore, mitigating the incidents is important and time critical. In practice, a document describing a mitigation process, called a troubleshooting guide (TSG), is usually used to reduce the Time To Mitigate (TTM). To investigate the usage of TSGs in real-world online services, we conduct the first empirical study on 18 real-world, large-scale online service systems in Microsoft. We analyze the distribution and characteristics of TSGs among all incident records in the past two years. According to our study, 27.2% incidents have TSG records and 36.2% of them occurred at least twice. Besides, on average developers spend around 36.3% of the entire mitigation time on locating the desired TSGs.

Integrity signals

Registry

Crossref · 10.1145/3368089.3417054

Cites

6 of 6 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Queries, dashboards, validators, runbooks, ticketing systems, change windows, approvals, and audit trails still define what can be safely done.

    “Queries, dashboards, validators, runbooks, ticketing systems, change windows, approvals, and audit trails still define what can be safely done [4], [5], [72], [70], [73], [55].”
  • Once an agent proposes mitigations, the system becomes a socio-technical control loop, and the failure mode is no longer wrong answer but wrong change at the wrong time.

    “Once an agent proposes mitigations (restart, failover, throttling, config toggle), the system becomes a socio-technical control loop.The failure mode is no longer wrong answer but wrong change at the wrong time [4], [72], [105], [85].”
  • Trusted systems leave traces that can be reviewed, act with care during uncertainty, and recover when things go off plan.

    “trusted systems leave traces that can be reviewed, act with care during uncertainty, and recover when things go off plan [72], [11], [105], [4].”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Jiang, J., Lu, W., Chen, J., Lin, Q., Zhao, P., Kang, Y., Zhang, H., Xiong, Y., Gao, F., Xu, Z., Dang, Y., & Zhang, D.
Affiliations
  • Tianjin University (CN)
  • Peking University (CN)
  • Microsoft Research Asia (China) (CN)
  • University of Newcastle Australia (AU)
  • Microsoft (United States) (US)
Venue
Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering
Publisher
ACM
Published
2020-11-08
Pages
1410-1420
OpenAlex
W3086623952
Cited by
56
References
6
Citations by year
2026: 4 · 2025: 9 · 2024: 17 · 2023: 5 · 2022: 11 · 2021: 7 · 2020: 3
FWCI
5.45
Type
conference paper
Language
en
Open access
closed
Locations
  • ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) (publishedVersion)
  • NOVA (University of Newcastle Australia) (submittedVersion)
Topics
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
troubleshooting guide, incident mitigation, online service systems, service availability, outages, software maintenance

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review