Use Error Budget Report to convey Infradev Issues that have missed SLO
In the related issue, we consolidated the contents of the Error Budget report with the contents of the Infradev Report. A reminder that we did this because:
We've received feedback that having two reports with similar data is confusing.
Because of the different cadence in generating the reports they can often contain different data
and teams are finding it hard to make decisions when they are sure which report to use.At the time, we relied on the Engineering Allocation meeting to communicate Infradev issues that had missed their SLO, but with this meeting being removed there is no replacement yet for communication about these issues.
Proposal
- Rename the Error Budget Report to be the Error Budget and Infradev Report
- Include the past-due Infradev count (see below)
- Update the "Related Incidents" column to be a count with search (see below)
- Update the handbook to reflect these changes and how they are expected to be used
Past-due Infradev count
The cell currently includes a number of Infradev issues. Let's update that to be the total, followed by the overdue. The cell would read: x (with y overdue) where x and y are linked numbers that take the user to the relevant issue search.
Related Incidents
Despite looking at this report often, I still don't connect the emojii with severity. Please can we change this to be a linked number that takes the user to the relevant search?
If there was a severity1 issue, we could call that out specifically with the severity label and link to the incident.
Handbook changes
-
Find existing places where this is referenced and update for relevance (for example, https://about.gitlab.com/handbook/engineering/workflow/#infradev) -
Add a section with the steps for the reporters that detail what actions are taken on the 3rd of each month -
Add a section for the expected use of the report -
Add text about what is expected from EM/PMs on receipt of the report.