Monitor:Respond Weekly Update - W13 - Mar-27-2023
| | | |
Highlights
Going into the week
-
test task -
test task2
20% (60% of ~frontend, -20% of ~backend)
For the week of Monday, 2023-03-27.
- ~frontend: max of 1 engineers, 5 days in week
3(days) = 5(days) - 2(PTO)
- ~backend: max of 1 engineers, 5 days in week
-1(days) = 5(days) - 6(PTO)
Data from: Monitor:Respond Group Calendar, via Google App Scripts
4 Rollover issues from %"15.3", %"15.10", %"15.9"
%"15.3" rollover:
%"15.10" rollover:
%"15.9" rollover:
-
Phase 1: Add `/gitlab incident close` Slack sla... (gitlab-org/gitlab#374958)
rkadam3
-
Phase 1: Add `/gitlab incident comment <text>` ... (gitlab-org/gitlab#374957)
rkadam3
Data from: GitLab REST API. Contains open issues which are in a prior milestone & assigned to a ~"group::respond" engineer.
15.11 focus area distribution
85% ~"type::maintenance" | 10% ~"type::feature" | 5% ~"type::bug" |
---|---|---|
65% ~"maintenance::removal" 18% ~"maintenance::refactor" 12% w/o sub-type 6% ~"maintenance::usability" |
50% w/o sub-type 50% ~"feature::addition" |
100% ~"bug::vulnerability" |
35% ~"Monitor: Metrics Deprecation" | 25% ~"Monitor:Self-Monitoring Deprecation" | 20% w/o epic |
----- | ----- | ----- |
71% ~"backend" 14% ~"frontend" 14% w/o eng label |
60% ~"backend" 20% ~"frontend" 20% w/o eng label |
75% w/o eng label 25% ~"backend" |
What got done this week?
More info...
Relevant links
- Current Planning Issue
- Async Retrospectives
- Internal dogfooding adoption (chart)
- Dogfooding by feature (table)
- Support Help Requests
- Ops Department Status Updates
/milestone %"15.11"
/label ~"group::respond" ~"devops::monitor" ~"section::ops" ~"type::ignore" ~"OpsSection::Weekly-Update"
This update was generated by the weekly_update script in gitlab-org/monitor/respond.
How does it work?
Where does the content come from?
Highlights are added manually; everything else is pulled from GitLab, Google, Grafana, etc.
How does it get there?
- Every Friday, a scheduled pipeline creates the issue for the next week, and it updates the issue for the current week.
- When a new issue is created, only a few details are included in the description about what might be expected for the week. A comment thread is added where highlights can be collected to be autofilled into the description later in the week.
- When the issue is updated, the highlights thread will be collected as a list and added to the issue description. An detailed overview of progress on the milestone will also be included.
How do I make changes?
To this specific issue
This specific issue: Add content directly to the issue description, or you can add highlights by commenting on the highlights thread.
Format
Static content: Update weekly-update.md. Add any static content to the file to include it in the issue description when the issue is created.
Dynamic content: Rearrange the REPLACE-ME
placeholder HTML comments. Placeholder comments can be either singleline or multiline. The placeholders are replaced by script-aggregated content.
- Required attributes:
-
section
: all-caps name given to a chunk of markdown generated by the weekly_update script.-
NAVIGATION
-> Link to previous/next update issue -
CAPACITY
-> PTO breakdown for Monitor:Respond team for the week -
ERROR-BUDGET
-> Current state of respond error budget -
ISSUE-DISTRIBUTION
-> Breakdown of team's focus by type label & epic -
PROGRESS-SUMMARY
-> Estimated % completion of scheduled issues by epic -
PROGRESS-DETAIL
-> Estimated % completion of each individual scheduled issue -
TEAM-ACTIVITY
-> Aggregated contributions for each team member over the last week -
ROLLOVER
-> Issues assigned to team members in expired milestones -
TEAM-LINKS
-> Link to planning issue & other team-specifics that change week to week -
QUICK-ACTIONS
-> Assigns milestone & other team-specifics that change week to week -
HIGHLIGHTS
-> List of comments from highlight thread (oldest thread to include the word "highlight" in the first comment)
-
-
action
: determines when the comment will be replaced in the issue description.-
CREATE
- replaced when the issue is created -
UPDATE
- replaced at the end of the week
-
-
- Singleline format:
<!-- REPLACE-WITH-<section>:<action> -->
- Multiline format:
-
<!-- REPLACE-WITH-<section>-START:<action> --> Anything here will also be replaced when the script runs. <!-- REPLACE-WITH-<section>-END:<action> -->
-
Adding threads: Add a multiline placeholder with section
of THREAD
. Content inside the block will be added as a thread on the issue, and it can include other placeholders.