Monitor:Respond Weekly Update - W17 - Apr-24-2023
< previous update | next update > |
---|
What is the team currently focused on?
Our highest priority is to complete feature removals scheduled for 16.0: Metrics, Self-Monitoring, and Embed Grafana Panels. We are confident to complete these on time.
In parallel, we are ramping up to Service Desk development by working on small bugs and feature requests.
Milestone plan: Monitor:Respond 16.0 Planning issue (#207 - closed)
Highlights
- HIGHLIGHT: Congratulation to @rkadam3 who was promoted to Senior Backend Engineer! You can check out his promotion document here.
- @kbychu created a component diagram of Service Desk to frame his vision for Service Desk. There is more to explore and refine (gitlab-org&8769), but our initial priorities will likely be Ticket Management followed by Queue Management. Recording is here.
- We fixed a bug that made Service Desk users understandably worrisome when editing internal notes - gitlab-org/gitlab#399828
- The GitLab CLI now supports reopening incidents with
glab incident reopen
- Our team has reviewed 10 Hackathon MRs. Thank you @splattael and @ck3g for supporting the community!
Going into the week
Capacity: 77% (40% of frontend, 95% of backend)
For the week of Monday, 2023-04-24.
Data from: Monitor:Respond Group Calendar, via Google App Scripts
0 Rollover issues from
Data from: GitLab REST API. Contains open issues which are in a prior milestone & assigned to a grouprespond engineer.
16.0 focus area distribution
90% typemaintenance | 5% typefeature | 5% typebug |
---|---|---|
78% maintenanceremoval 22% maintenancerefactor |
100% featureaddition | 100% w/o sub-type |
45% Monitor: Metrics Deprecation and Removal (gitlab-org&10107) | 30% Monitor:Self-Monitoring Deprecation and Removal (gitlab-org&10030 - closed) | 15% Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed) | 10% w/o epic |
---|---|---|---|
56% backend 22% frontend 11% backend frontend 11% w/o eng label |
50% backend frontend 33% backend 17% w/o eng label |
67% w/o eng label 33% backend frontend |
50% w/o eng label 50% backend frontend |
End of week progress snapshot
~49% complete of 16.0 scheduled work
- 82% - of scheduled issues without an epic
- 28% - of scheduled issues from epic: Monitor: Metrics Deprecation and Removal (gitlab-org&10107)
- 0% - of scheduled issues from epic: Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed)
- 74% - 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...
Standalone issues - 82% complete
Monitor: Metrics Deprecation and Removal - 28% complete
Engineering Transition issue for Service Desk to Monitor - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Service Desk: update team references in Enginee... (gitlab-org/gitlab#398168 - closed) Type: typemaintenance maintenancerefactor Domains: |
No assignee workflowready for development |
0% |
Service Desk: move Grafana panels to Respond da... (gitlab-org/gitlab#398166 - closed) Type: typemaintenance maintenancerefactor Domains: |
No assignee workflowready for development |
0% |
Service Desk: update ownership of metrics (gitlab-org/gitlab#398163 - closed) Type: typemaintenance maintenancerefactor Domains: backend frontend |
No assignee workflowready for development |
0% |
Monitor:Self-Monitoring Deprecation and Removal - 74% complete
Contributions on: 119 merge_requests, 35 issues
Contributions span from 2023-04-21 to 2023-04-29.
tristan.read focus areas
- Type: 78% typemaintenance, 19% typefeature, 3% other (<3% each)
- Group: 22% groupux paper cuts, 14% grouppipeline authoring, 14% grouprespond, 14% groupsecurity policies, 11% grouprunner, 8% groupproject management, 19% other (<3% each)
- Category: 14% Category:Continuous Integration, 11% ~"Category:Runner Fleet", 11% Category:Secrets Management, 8% Category:Team Planning, 5% Category:Incident Management, 3% Category:Security Policy Management, 49% other (<3% each)
- Work item: 92% ~"merge_requests", 8% issues
grouprespond contributions
merge_requests
- Hide metrics shortcuts behind : commented on (3), opened (1) issues
- Clean up presentation of items in incident high... (gitlab-org/gitlab#360009 - closed) : commented on (1)
other contributions
merge_requests
- Activity sort filter dropdown migration : accepted (5), commented on (18), approved (6)
- Makes @leipert a frontend maintainer : approved (1) issues
- rspec-all frontend_fixtures as-if-foss sometime... (gitlab-org/gitlab#407588 - closed) : commented on (1), closed (1)
psjakubowska focus areas
- Type: 73% typefeature, 27% typemaintenance
- Group: 64% groupcompliance, 27% grouprespond, 9% groupanti-abuse
- Category: 64% Category:Audit Events, 27% Category:Metrics, 9% other (<3% each)
- Work item: 100% ~"merge_requests"
grouprespond contributions
merge_requests
- Draft: Add early returns when initiating : commented on (2), opened (1)
other contributions
merge_requests
- Resolve "Remove page-wide reload on audit : commented on (7), approved (1)
splattael focus areas
- Type: 70% typemaintenance, 16% typefeature, 5% typebug, 8% other (<3% each)
- Group: 23% grouprespond, 7% groupfoundations, 5% groupimport and integrate, 3% groupcompliance, 3% groupthreat insights, 3% ~"group::release", 2% groupsource code, 55% other (<3% each)
- Category: 5% Category:Internationalization, 3% Category:Source Code Management, 92% other (<3% each)
- Work item: 86% ~"merge_requests", 14% issues
grouprespond contributions
merge_requests
-
Add convenience helper method
safe_format
: commented on (49), opened (10), accepted (1), approved (1) - Upgrade to RuboCop 1.50.2 : opened (1) issues
- Escalation Policy edit modal: `Save changes` bu... (gitlab-org/gitlab#376697 - closed) : commented on (1)
other contributions
merge_requests
- Add Gitlab::Source for referencing Gitlab : accepted (28), commented on (101), opened (2), approved (33)
- Use unauthenticated GitLab client for : commented on (8), approved (3)
- Adding containerSecurityContext logic to : commented on (2) issues
- Upgrade pg to 1.5.X after fixing core dumps due... (gitlab-org/gitlab#408982 - closed) : commented on (27), opened (7), closed (1)
- Thursday 2023-04-27 15:24 UTC - `gitlab-org/git... (gitlab-org/quality/engineering-productivity/master-broken-incidents#1534 - closed) : commented on (3)
- Enable Style/MethodCallWithArgsParentheses (gitlab-org/ruby/gems/gitlab-styles#57) : opened (1)
syasonik focus areas
- Type: 42% typefeature, 21% typemaintenance, 21% typebug, 5% typeignore, 11% other (<3% each)
- Group: 89% grouprespond, 11% other (<3% each)
- Category: 47% Category:Service Desk, 11% Category:Metrics, 11% Category:Incident Management, 32% other (<3% each)
- Work item: 95% ~"merge_requests", 5% issues
grouprespond contributions
merge_requests
- Introduce ff for deprecating Monitor Metrics : commented on (14), opened (2) issues
- Monitor:Respond Weekly Update - W16 - Apr-17-2023 (#232 - closed) : commented on (1)
ck3g focus areas
- Type: 58% typemaintenance, 38% typefeature, 4% other (<3% each)
- Group: 46% grouprespond, 20% groupcode review, 6% groupthreat insights, 4% groupsecurity policies, 4% ~"group::application performance", 2% groupanalytics instrumentation, 18% other (<3% each)
- Category: 31% Category:GitLab CLI, 4% Category:Security Policy Management, 65% other (<3% each)
- Work item: 99% ~"merge_requests", 1% other (<3% each)
grouprespond contributions
merge_requests
- Layout/ArgumentAlignment: Fix silenced : commented on (17), approved (1), opened (11), accepted (1)
- feat(incident): add incident reopen command : commented on (7), opened (1) issues
- feat: incident reopen command (gitlab-org/cli#1314 - closed) : opened (1)
other contributions
merge_requests
- Use project bot users to run scan execution : commented on (13), approved (7), accepted (3)
- feat(ssh-key): add delete command : commented on (17)
- don't mount token when tokens not set : commented on (1)
- Fix Dr Jeb Hurley building trust broken link : commented on (2), approved (2)
rkadam3 focus areas
- Type: 46% typefeature, 41% typemaintenance, 9% typebug, 4% other (<3% each)
- Group: 77% grouprespond, 7% groupproduct analytics, 4% groupcompliance, 4% groupanti-abuse, 4% groupimport and integrate, 5% other (<3% each)
- Category: 34% Category:Service Desk, 7% ~"Category:Product Analytics", 4% Category:Audit Events, 4% Category:Integrations, 52% other (<3% each)
- Work item: 73% ~"merge_requests", 27% issues
grouprespond contributions
issues
- Service Desk Issue Url Placeholder (gitlab-org/gitlab#408793 - closed) : commented on (10), closed (3) merge_requests
- Add attribution to external participant : commented on (28), opened (2)
other contributions
merge_requests
- Ensuring redundant group update audit events : accepted (2), approved (4), commented on (4), opened (1) issues
- [Feature flag] Rollout of `external_note_author... (gitlab-org/gitlab#408932 - closed) : opened (2)
francoisrose focus areas
- Type: 63% typeignore, 13% typefeature, 25% other (<3% each)
- Group: 100% grouprespond
- Category: 38% Category:Service Desk, 63% other (<3% each)
- Work item: 100% issues
grouprespond contributions
issues
- Monitor:Respond 16.0 Planning issue (#207 - closed) : commented on (3)
- GitLab Service Desk JTBD (gitlab-org/gitlab#394968 - closed) : commented on (3)
- Feature flags requiring attention for group::re... (gitlab-org/quality/triage-reports#11848 - closed) : closed (1), commented on (1)
other contributions
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
.