{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T04:33:28Z","timestamp":1750221208599,"version":"3.41.0"},"reference-count":2,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2018,8,1]],"date-time":"2018-08-01T00:00:00Z","timestamp":1533081600000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2018,8]]},"abstract":"<jats:p>SRE (site reliability engineering) is a job function, a mindset, and a set of engineering approaches for making web products and services run reliably. SREs operate at the intersection of software development and systems engineering to solve operational problems and engineer solutions to design, build, and run large-scale distributed systems scalably, reliably, and efficiently. A mature SRE team likely has well-defined bodies of documentation associated with many SRE functions. If you manage an SRE team or intend to start one, this article will help you understand the types of documents your team needs to write and why each type is needed, allowing you to plan for and prioritize documentation work along with other team projects.<\/jats:p>","DOI":"10.1145\/3277539.3283589","type":"journal-article","created":{"date-parts":[[2018,11,13]],"date-time":"2018-11-13T13:20:16Z","timestamp":1542115216000},"page":"66-91","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":1,"title":["Why SRE Documents Matter"],"prefix":"10.1145","volume":"16","author":[{"given":"Shylaja","family":"Nukala","sequence":"first","affiliation":[{"name":"Google"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Vivek","family":"Rau","sequence":"additional","affiliation":[{"name":"Google"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2018,8]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"Blank-Edelman D. N. 2018. Seeking SRE: Conversations About Running Production Systems at Scale. O'Reilly Media.  Blank-Edelman D. N. 2018. Seeking SRE: Conversations About Running Production Systems at Scale. O'Reilly Media."},{"key":"e_1_2_1_2_1","unstructured":"Murphy N. Beyer B. Jones C. Petoff J. 2016. Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media.   Murphy N. Beyer B. Jones C. Petoff J. 2016. Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3277539.3283589","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3277539.3283589","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T01:39:38Z","timestamp":1750210778000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3277539.3283589"}},"subtitle":["How documentation enables SRE teams to manage new and existing services"],"short-title":[],"issued":{"date-parts":[[2018,8]]},"references-count":2,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2018,8]]}},"alternative-id":["10.1145\/3277539.3283589"],"URL":"https:\/\/doi.org\/10.1145\/3277539.3283589","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2018,8]]},"assertion":[{"value":"2018-08-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}