SRE planning

[ShellyXueHan]

Describe the issue Identify SRE implementation progress and missing components, plan on follow ups

Definition of done

• [ ] discussion and backlog grooming
• [ ] plan for next quarter
• [ ] share with team and get feedback

[w8896699]

SRE Implementation Plan

1. Example with Registry App:

• Objective: Develop internal SLIs, set up SLAs, and define an error budget for the Registry application.

• Actions:

  1. Collaborate with the Registry service lead to identify critical SLIs (e.g., response time, error rate).
  2. Set realistic SLAs based on historical performance and user expectations.
  3. Define an error budget that balances feature development with reliability.
  4. Establish monitoring and alerting for the identified SLIs.
  5. Discuss and finalize SLA and error budget details with the Registry team.

2. Team Collaboration:

• Objective: Collaborate with development teams to balance feature development and reliability.

• Actions:

  1. Invite all developers from the Registry app for a collaborative session.
  2. Present the developed SLIs, SLAs, and error budgets.
  3. Discuss the importance of balancing feature development with meeting reliability targets.
  4. Encourage input and feedback from the development team.
  5. Establish a culture of shared responsibility for system reliability.

3. Service Lead Involvement:

• Objective: Extend the process to other applications with different service leads.

• Actions:

  1. Share the example metrics and documentation with other Service Leads.
  2. Collaborate with each service lead to identify application-specific SLIs.
  3. Help them set realistic SLAs and error budgets.
  4. Facilitate discussions on balancing feature development and reliability for each application.
  5. Document SLIs, SLAs, and error budgets for each application.

4. Agreements and Risk Mitigation:

• Objective: Set agreements for application availability and establish risk mitigation strategies.

• Actions:

  1. Repeat collaborative sessions with other Service Leads to finalize SLAs and error budgets.
  2. Clearly communicate the importance of maintaining services until the budget is exhausted.
  3. Discuss risk mitigation strategies in case of potential service interruptions.
  4. Establish clear guidelines for updating services and communicating potential risks.

5. Documentation and Review:

• Objective: Document agreements and practices for future reference and improvement.

• Actions:

  1. Conclude the process by documenting all SLIs, SLAs, error budgets, and agreements in the SRE repository.
  2. Set a review date for the documentation, agreements, and SLIs (twice a year).
  3. Encourage continuous improvement based on learnings and changes in application requirements.
  4. Update documentation as needed and ensure it remains a valuable reference for the team.