Monitor:Respond Weekly Update - W13 - Mar-27-2023
< previous update | next update > |
---|
Highlights
- This has been a quiet week, with lots of people in the team being out of office. Next week will be similar. You can see who's out when by viewing the Monitor Stage calendar.
- The team is making progress on our 15.11 goals.
- HIGHLIGHT: We're collecting Service Desk dogfooding opportunities. We also discovered several existing use-cases at GitLab: Account Deletion requests, CES, People Connect, Support.
- A vulnerability fixed by @splattael has now been shipped in the latest Security Releases.
- HIGHLIGHT: @rkadam3 recorded a demo for declaring incidents via Slack. This feature was recently released as open beta. Check it out on GitLab Unfiltered: https://youtu.be/H_wdLb8XLFU
- After releasing Incident Tags a month ago, we have now removed the feature flag and completed the rollout for this feature.
Going into the week
Capacity: 73% (80% of frontend, 70% of backend)
For the week of Monday, 2023-03-27.
-
frontend: max of 2 engineers, 5 days in week
8(days) = 10(days) - 2(PTO)
-
backend: max of 4 engineers, 5 days in week
14(days) = 20(days) - 6(PTO)
Data from: Monitor:Respond Group Calendar, via Google App Scripts
5 Rollover issues from %15.9, %15.10
%15.9 rollover:
-
Upgrade httparty to 0.21 (gitlab-org/gitlab#389079 - closed)
splattael
-
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
%15.10 rollover:
-
Validate that feature_categories are correct (gitlab-org/gitlab#381882 - closed)
splattael
-
Add a pagerduty icon as an option for relating ... (gitlab-org/gitlab#393261)
rkadam3
Data from: GitLab REST API. Contains open issues which are in a prior milestone & assigned to a grouprespond engineer.
15.11 focus area distribution
90% typemaintenance | 10% typefeature |
---|---|
67% maintenanceremoval 17% maintenancerefactor 11% w/o sub-type 6% maintenanceusability |
50% w/o sub-type 50% featureaddition |
35% Monitor: Metrics Deprecation and Removal (gitlab-org&10107) | 30% Monitor:Self-Monitoring Deprecation and Removal (gitlab-org&10030 - closed) | 15% w/o epic" | 10% Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed) | 5% Slack workflow service desk ticket creation (gitlab-org&10041 - closed) | 5% Incident Tag MVC (gitlab-org&8741) |
---|---|---|---|---|---|
71% backend 14% backend frontend 14% w/o eng label |
50% backend frontend 33% backend 17% w/o eng label |
33% backend 33% backend frontend 33% frontend |
50% backend frontend 50% w/o eng label |
100% w/o eng label | 100% backend frontend |
End of week progress snapshot
~49% complete of 15.11 scheduled work
- 16% - of scheduled issues from epic: Monitor: Metrics Deprecation and Removal (gitlab-org&10107)
- 88% - of scheduled issues without an epic
- 31% - of scheduled issues from epic: Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed)
- 100% - of scheduled issues from epic: Incident Tag MVC (gitlab-org&8741)
- 70% - of scheduled issues from epic: Slack workflow service desk ticket creation (gitlab-org&10041 - closed)
- 35% - of scheduled issues from epic: Monitor:Self-Monitoring Deprecation and Removal (gitlab-org&10030 - closed)
Percentage is a rough estimate and could be quite wrong. The calculation codifies @syasonik
's mental model for ~% completion, based on workflow labels, open MRs, and domain labels.
More info...
Monitor: Metrics Deprecation and Removal - 16% complete
Standalone issues - 88% complete
Engineering Transition issue for Service Desk to Monitor - 31% complete
Incident Tag MVC - 100% complete
Issue | Status | ~% Complete |
---|---|---|
Remove references to the `incident_event_tags` ... (gitlab-org/gitlab#398130 - closed) Type: typemaintenance Domains: backend frontend documentation Possible action items required- check for missing subtype label |
@ck3g No frontend assignee workflowin review Relevant MRs: (1) Merged MRs (1): gitlab-org/gitlab!115834 (merged) |
100% |
Slack workflow service desk ticket creation - 70% complete
Issue | Status | ~% Complete |
---|---|---|
Technical Breakdown: Slack workflow service des... (#214 - closed) Type: typefeature Domains: |
@rkadam3 workflowin review |
70% |
Monitor:Self-Monitoring Deprecation and Removal - 35% complete
Issue | Status | ~% Complete |
---|---|---|
Update documentation related to self-monitoring... (gitlab-org/gitlab#394998 - closed) Type: typemaintenance maintenanceremoval Domains: documentation Possible action items required- check workflow label for accuracy - actual is |
@rkadam3 workflowin dev |
25% |
Remove self_monitor_form.vue component and rela... (gitlab-org/gitlab#394992 - closed) Type: typemaintenance maintenanceremoval Domains: frontend backend |
@rkadam3 workflowin dev Relevant MRs: (1) Draft MRs (1): gitlab-org/gitlab!114980 (merged) |
40% |
Contributions on: 39 merge_requests, 23 issues, 2 epics
Contributions span from 2023-03-24 to 2023-04-01.
tristan.read focus areas
- Type: 57% typefeature, 43% other (<3% each)
- Group: 43% grouprespond, 14% groupacquisition, 43% other (<3% each)
- Category: 43% Category:Incident Management, 57% other (<3% each)
- Work item: 57% ~"merge_requests", 43% issues
grouprespond contributions
merge_requests
- Rolls out incident_event_tags feature : commented on (2), approved (1)
other contributions
merge_requests
- Add reveal-conceal password option : commented on (1) issues
- New incident (tristan.read/test-incident-tags#1 - closed) : closed (2), opened (1)
psjakubowska focus areas
- Type: 63% typemaintenance, 25% typefeature, 13% typebug
- Group: 46% grouprespond, 25% groupux paper cuts, 13% groupcode review, 8% groupacquisition, 8% groupfoundations
- Category: 38% Category:Code Review Workflow, 21% Category:Metrics, 17% Category:On-call Schedule Management, 8% Category:Service Desk, 8% ~"Category:Conversion Experiment", 8% other (<3% each)
- Work item: 83% ~"merge_requests", 17% issues
grouprespond contributions
issues
- Service Desk: Attribute comment authorship for ... (gitlab-org/gitlab#226995 - closed) : commented on (3), closed (1) merge_requests
- Resolve "Unbox on-call schedule UI" - : commented on (5), opened (2)
other contributions
merge_requests
- File-by-file: Add action for async : commented on (9), approved (2)
- chore: Simplify compound SCSS selector : commented on (2)
splattael focus areas
- Type: 100% other (<3% each)
- Group: 100% grouprespond
- Category: 100% other (<3% each)
- Work item: 100% ~"merge_requests"
other contributions
syasonik focus areas
- Type: 48% typefeature, 16% typebug, 8% typemaintenance, 28% other (<3% each)
- Group: 60% grouprespond, 12% groupsource code, 28% other (<3% each)
- Category: 24% Category:Service Desk, 20% Category:Incident Management, 12% Category:Source Code Management, 8% Category:Metrics, 36% other (<3% each)
- Work item: 56% issues, 40% ~"merge_requests", 4% epics
grouprespond contributions
issues
- Project dropdown in incident modal for Slack is... (gitlab-org/gitlab#403570) : commented on (4), opened (1)
- Technical Breakdown: Slack workflow service des... (#214 - closed) : commented on (6) merge_requests
- Add quick action to add thread when opening : opened (1), commented on (1), closed (1) epics
- Monitor: Metrics Deprecation and Removal (gitlab-org&10107) : commented on (1)
other contributions
merge_requests
- Fork fetch upstream improvements : commented on (2), approved (1)
- Clean up a couple broken styles and headers : accepted (2), opened (1), commented on (1) issues
- Improve Monitor stage & team demo sharing (general#76 - closed) : closed (1)
- Prometheus Training - Sarah Yasonik (training#6 - closed) : closed (1)
- FY2022 Monitor:Respond Accomplishments (#191 - closed) : closed (1)
ck3g focus areas
- Type: 51% typefeature, 36% typemaintenance, 9% typebug, 4% other (<3% each)
- Group: 36% grouprespond, 17% groupfoundations, 9% ~"group::authentication and authorization", 9% groupsource code, 4% groupproject management, 4% groupstatic analysis, 4% grouppackage registry, 17% other (<3% each)
- Category: 13% Category:Incident Management, 9% Category:Source Code Management, 4% Category:GitLab CLI, 4% Category:GDK, 4% Category:Service Desk, 4% Category:SAST, 4% Category:Package Registry, 58% other (<3% each)
- Work item: 94% ~"merge_requests", 6% issues
grouprespond contributions
merge_requests
-
feat(incident): add
incident close
command : opened (1) - Fix Layout/ArgumentAlignment offenses in : commented on (12), opened (4) issues
- feat: incident close command (gitlab-org/cli#1295 - closed) : opened (1)
- Document Incident Timeline Events from Labels (gitlab-org/gitlab#398678 - closed) : commented on (1)
other contributions
merge_requests
- Improve gmail app password documentation : commented on (1), approved (1)
- Make menu items in new navigation sidebar : commented on (21), approved (6), accepted (2)
- Update INONESIAN17 : commented on (1), closed (1) issues
- Investigate why certain merge requests don't ha... (gitlab-org/gitlab#342508 - closed) : commented on (1)
rkadam3 focus areas
- Type: 45% typefeature, 30% typemaintenance, 15% typebug, 10% other (<3% each)
- Group: 50% grouprespond, 25% ~"group::integrations", 15% groupstatic analysis, 5% groupoptimize, 5% groupthreat insights
- Category: 30% Category:Service Desk, 25% Category:Integrations, 15% Category:Incident Management, 15% Category:Secret Detection, 5% Category:Vulnerability Management, 10% other (<3% each)
- Work item: 40% ~"merge_requests", 35% issues, 25% epics
grouprespond contributions
issues
- Implement event handlers for Slack workflow step (gitlab-org/gitlab#403003 - closed) : opened (2) epics
- Slack workflow service desk ticket creation (gitlab-org&10041 - closed) : commented on (5) merge_requests
- [Draft: Initial commit for reference DO NOT : opened (1), commented on (1), approved (1)
other contributions
merge_requests
- Fix broken VSD link from subgroup : commented on (3), accepted (1), approved (1) issues
- Move all supporting code for the GitLab Slack a... (gitlab-org/gitlab#355896 - closed) : commented on (5)
francoisrose focus areas
- Type: 21% typemaintenance, 21% typefeature, 18% typeignore, 7% typebug, 32% other (<3% each)
- Group: 86% grouprespond, 14% other (<3% each)
- Category: 39% Category:Service Desk, 7% Category:Metrics, 4% Category:Incident Management, 50% other (<3% each)
- Work item: 68% issues, 25% ~"merge_requests", 7% epics
grouprespond contributions
merge_requests
- Remove "focus area" table from planning : commented on (2), accepted (1), opened (1) issues
- Monitor:Respond 15.11 Planning issue (#206 - closed) : commented on (9), closed (1)
- Service Desk: handoff maintainer reviews (gitlab-org/gitlab#398167 - closed) : commented on (7), closed (1) epics
- Slack workflow service desk ticket creation (gitlab-org&10041 - closed) : commented on (1)
- Monitor: Metrics Deprecation and Removal (gitlab-org&10107) : commented on (1)
other contributions
merge_requests
- Draft: GitLab Service Desk Direction Review : commented on (1), accepted (1), opened (1) issues
- PM Coverage for Kevin Chu from 2023-03-29 to 20... (gitlab-com/Product#5591 - closed) : commented on (1)
Data from: Scraped from activity page for each user. Activities which don't support labels are mostly ignored.
Relevant links
- Current Planning Issue
- Async Retrospectives
- Internal dogfooding adoption (chart)
- Dogfooding by feature (table)
- Support Help Requests
- Ops Department Status Updates
This update was generated by the weekly_update script in gitlab-org/monitor/respond Highlights are manually curated.
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.
Content
Run the Generate detailed weekly update issue
to trigger an update. Once an update has run, the pipeline can be run many
times without consequence to the existing issue. Refer to Format > Dynamic content
for the syntax needed
to regenerate sections of the issue.
To modify how the content itself is generated, refer to weekly_update/README.md
.