I beg to differ with this:
“SRE also sets Service Level Indicators (SLIs), Service Level Objectives (SLOs), Service Level Agreement (SLA)”
Google SRE book: “...the product team and the SRE team select an appropriate availability target for the service and its user base, and the service is managed to that SLO. Deciding on such a target requires strong collaboration from the business.”
Service level related stuff is tied to the business so tightly, that virtually no business is gonna let an SRE decide on SLA. Maybe SREs can advise on what could be used as an SLI to non-technical people, but to tell how the service should perform is not their job. It is to ensure it performs up to a certain level - SLO - which should be (and often is) given as an input to SRE teams.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I beg to differ with this:
“SRE also sets Service Level Indicators (SLIs), Service Level Objectives (SLOs), Service Level Agreement (SLA)”
Google SRE book: “...the product team and the SRE team select an appropriate availability target for the service and its user base, and the service is managed to that SLO. Deciding on such a target requires strong collaboration from the business.”
Service level related stuff is tied to the business so tightly, that virtually no business is gonna let an SRE decide on SLA. Maybe SREs can advise on what could be used as an SLI to non-technical people, but to tell how the service should perform is not their job. It is to ensure it performs up to a certain level - SLO - which should be (and often is) given as an input to SRE teams.