Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2337e61db364603

Jump to content

Talk:Site reliability engineering

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 26 days ago by Lizthegrey in topic SRE Agent

Why was it proposed for deletion?

[edit]

Site Reliability Engineering is a different approach to IT Engineering and was acknowledged by many companies other than Google. I would expect to see a meaningful discussion before there is a resolution. https://www.redhat.com/en/topics/devops/what-is-sre Ronnieroxx (talk) 14:44, 17 June 2021 (UTC)Reply

Site reliability engineering is one of the hottest job titles right now. https://techbeacon.com/enterprise-it/what-it-takes-be-site-reliability-engineer is one such source indicating that 22% of IT organizations have a role titled "SRE" these days. https://techcrunch.com/2016/03/02/are-site-reliability-engineers-the-next-data-scientists/ Lizthegrey (talk) 15:01, 17 June 2021 (UTC)Reply

Google came up with SRE, links are to Google. Just like links about the Toyota Production System would, presumably, link to Toyota. That's not a reason NOT to have a wikipedia page about an industry trend, though.  Preceding unsigned comment added by 199.168.59.113 (talk) 15:35, 17 June 2021 (UTC)Reply

While SRE started at Google, right now there are job openings for SRE (even in Wikimedia ), Youtube videos , Conferences , and other resources (RedHat, Atlassian, Microsoft). A better list is here. I'd argue that the article needs to be expanded considerably. (Full disclosure/disclaimer: I'm currently a Google SRE, commenting for myself, not representing Google). sharhalakis 16:00, 17 June 2021 (UTC)Reply

I've removed the tag, cleaned up the article, and added further references to non-Google sources. I am a software engineer by trade, but I don't and have never worked for Google (unless you count Google Summer of Code years ago, but I don't). GorillaWarfare (she/her  talk) 17:46, 17 June 2021 (UTC)Reply
It's a good start but I agree the article should be expanded considerably. Jtingiris (talk) 19:14, 7 February 2024 (UTC)Reply

Time to remove the "multiple issues" slur?

[edit]

While the article would benefit from additional information on this large topic, I believe that it's time to remove the "multiple issues" slur. I request that anyone who believes these warnings still apply to reconsider and perhaps remove them if they are now satisfied with the article so far. Respectfully, HowardBGolden (talk) 17:48, 16 June 2024 (UTC)Reply

Any user without a conflict of interest can remove maintenance notices. If someone reverts your removal, then you're expected to discuss on the talk page. Also, I wouldn't call it a "slur", it is a label about the quality of the page. lizthegrey (talk) 21:53, 16 June 2024 (UTC)Reply

Addressing the buzzword tag (May 2023)

[edit]

The article has carried a buzzword maintenance tag since May 2023, and I would like to work towards resolving it. I suspect Deployment subsection in particular seems to be the main source of the issue.

I plan to rewrite these sections to be more direct. If anyone has suggestions or sources I should cite for these happy to discuss and anchor to specific language. Akolamaverick (talk) 19:05, 29 June 2026 (UTC)Reply

would suggest relying on the various O'Reilly books on the subject as authoritative but without pulling directly from them or else you get the "kitchen sink sre" thing that was in the article earlier and was not DUE. lizthegrey (talk) 21:02, 29 June 2026 (UTC)Reply
Great project! Agree that working from reputably-published books is a good starting point. Three Google SRE books are available online for free, and there are good chunks of others available on Google Books, like Mastering Site Reliability Engineering in Enterprise. There are also some open access ACM Digital Library articles that look helpful, like this one about automation, this one about docs, and this one about teaching SRE. Dreamyshade (talk) 22:40, 29 June 2026 (UTC)Reply

SRE Agent

[edit]

or AI SRE or AI SRE agent; Azure, AWS, fuzzylabs It'd be good to have a section. ~2026-38073-05 (talk) 19:16, 3 July 2026 (UTC)Reply

We don't cover neologisms until reliable, secondary sources cover them. Do you have anything that's not from the creator of an "AI SRE Agent"? lizthegrey (talk) 21:56, 3 July 2026 (UTC)Reply