Key Duties of SRE

Key Duties of SRE:

1. Develop and manage system documentation

2. Design, build, and maintain the core infrastructure.

3. Diagnose the system and develop fixes.

4. Focus on writing software to automate processes and reduce toil.

5. Monitor performance

SRE team consist of:

- Availability

- Latency

- Performance

- Efficiency

- Change management

- Monitoring and alerting

- Emergency response

- Incident response

- Preparation

- Capacity planning

SRE’s strategic goals are to:

- Make deployment easier

- Improve or maintain uptime

- Establish visibility into the application performance

- Set SLI’s and SLO’s and Error Budgets

- Increase speed by assuming calculated risks

- Eliminate toil

- Reduce the cost of failure to lower new feature cycle time.

Reducing toil and controlling SRE team workloads:

Toil is tedious, manual, work perform by SRE teams. In your day to day work, whether you are a software developer or an architect you can be doing tasks that you do not enjoy. These are usually manual, boring and repetitive tasks that can lead to mistakes. SRE teams will also have to perform similar tasks. However, this is one instance the SREs can put their development skills in use and eliminate the manual processes as much as possible. It is a good practice to have SREs spend up to 50% of their time on improving the systems that they manage.