SRE

TL;DR:

• If you need help from SRE and it is an emergency, you can page us via https://klaxon.wikimedia.org.
• If it is not an emergency, but do not know which team is responsible for your question, just open a generic task on Phabricator in the SRE project and our Clinic Duty person of the week will route it. If it more urgent or just a quick check you can find us on IRC: #wikimedia-sre ^connect.

Site Reliability Engineering (SRE) is responsible for availability, performance, monitoring, emergency response, infrastructure security, and capacity planning, plus the maintenance of software used for that purpose. This is similar to what in many other organizations is handled by an Operations or System Administration team. SRE treats computer operations as a software problem and applies automation wherever possible. The Foundation has a number of sub-teams within SRE, each responsible for different areas. Check SRE Team Requests to see how to get in touch with those teams, and see mw:Wikimedia Site Reliability Engineering for a more detailed team structure.

• SRE Data Center Operations - all things related to Data Centers, hardware maintenance and purchases
• SRE Data Persistence - Databases and Object storage (MariaDB and Swift)
• SRE Infrastructure Foundations - Automation and Networking (cumin, netbox, puppet, spicerack)
• SRE Observability - Monitoring and Logging (Prometheus/Grafana and ElasticSearch, plus some Kafka)
• SRE Service Operations - MediaWiki Operations and Supporting Services (Kubernetes, memcached, redis, Infrastructure for: Gitlab, OTRS, Phabricator)
• SRE Traffic - Caching and DNS (ATS, varnish, GeoDNS, wikidough)

References:

• How complex systems fail This is where SRE works
• Google's SRE books Google formalized many of the concepts and coined the term SRE