Monitor:Respond Weekly Update - W16 - Apr-17-2023
< previous update | next update > |
---|
Highlights
- HTML-only emails are now parsed properly by Service Desk! Thank you @splattael and @msaleiko for collaborating on this tricky rollout. gitlab-org/gitlab#372301 (closed)
- @msedlakjakubowski revamped the Service Desk documentation, which now adheres to the GitLab CTRT Topic Types!
- The On-Call Schedule UI has been unboxed and looks really slick! Screenshots of the before/after are here: gitlab-org/gitlab!114482 (merged)
- HIGHLIGHT: @psjakubowska recorded a demo of Incident Event Tags on GitLab Unfiltered: https://www.youtube.com/watch?v=OF8HbFjirpU. Feel free to ask any questions in the Ops Showcase issue: gitlab-org/ci-cd/section-showcases#14 (closed)
- %15.11 is concluded, see below for the goals review and Say Do ratio.
- %16.0 planning is done, you can check out our goals here: #207 (closed)
%15.11 goals review
- Complete removals (by prepping MRs) so we have minimal work in 16.0:
- Metrics: gitlab-org&10107
- 🟢 Outcome: prep work is done and we are ready to remove Metrics in 16.0
- Self-monitoring: gitlab-org&10030 (closed)
- 🟢 Outcome: prep work is done and we are ready to remove Self-Monitoring in 16.0
- Metrics: gitlab-org&10107
- Slack workflow service desk ticket creation - gitlab-org&10041 (closed)
-
Outcome: goal was deprioritized mid-milestone, see #214 (comment 1339661538)
-
- Familiarize with Service Desk by doing:
- Onboarding issues identified by @msaleiko
- 🟡 Outcome: completed 50% of these
- Ownership transition issues identified by @francoisrose - gitlab-org&10127 (closed)
- 🟡 Outcome: completed 50% of these
- Onboarding issues identified by @msaleiko
grouprespond in %15.11 = 40%
Say Do ratio for- Say = 5 goals = goals committed to by the team at the start of the milestone.
- Do = 2 goals = goals which were achieved during the milestone.
Context:
- 1 goal was marked unachieved because it was deprioritized mid-milestone. This was the right call, but significant progress had been made including building a proof of concept Slack workflow. Context for deprioritization: #214 (comment 1339661538)
- 2 goals were marked unachieved because vaguely defined, yet progress was still made on them and they were partially achieved (see above).
Trend:
Going into the week
Capacity: 83% (80% of frontend, 85% of backend)
For the week of Monday, 2023-04-17.
Data from: Monitor:Respond Group Calendar, via Google App Scripts
28 Rollover issues from %15.11, %15.9
%15.11 rollover:
-
Metrics: Delete UI code for health tab in clust... (gitlab-org/gitlab#393926 - closed)
tristan.read
-
Clean up presentation of items in incident high... (gitlab-org/gitlab#360009 - closed)
tristan.read
-
[Feature flag] Rollout of `remove_monitor_metrics` (gitlab-org/gitlab#399248)
psjakubowska
-
Metrics: hide deprecated modules behind a featu... (gitlab-org/gitlab#399231 - closed)
psjakubowska
-
Fix spec violations in spec/frontend/monitoring... (gitlab-org/gitlab#391068 - closed)
psjakubowska
-
Fix spec violations in spec/frontend/monitoring... (gitlab-org/gitlab#391022 - closed)
psjakubowska
-
Fix spec violations in spec/frontend/monitoring... (gitlab-org/gitlab#390979 - closed)
psjakubowska
-
Fix spec violations in spec/frontend/monitoring... (gitlab-org/gitlab#391020 - closed)
psjakubowska
-
Unbox on-call schedule UI (gitlab-org/gitlab#387079 - closed)
psjakubowska
-
Service Desk: Attribute comment authorship for ... (gitlab-org/gitlab#226995 - closed)
rkadam3
-
https://gitlab.com/gitlab-org/gitlab/-/issues/389822+
splattael
-
RSpec: Provide a way to stub access level in po... (gitlab-org/gitlab#389247 - closed)
splattael
-
Service Desk config errors visible to non-admins (gitlab-org/gitlab#384530)
splattael
-
Validate that feature_categories are correct (gitlab-org/gitlab#381882 - closed)
splattael
-
🆕 RuboCop rule: Prevent hook/let definitions wi... (gitlab-org/ruby/gems/gitlab-styles#46 - closed)
splattael
-
HTML not parsed in Service Desk (gitlab-org/gitlab#372301 - closed)
splattael
-
Monitor:Respond Weekly Update - W15 - Apr-10-2023 (#230 - closed)
syasonik
-
Metrics: Delete GFM pipeline logic for embeds (gitlab-org/gitlab#397137 - closed)
syasonik
-
Metrics: Remove service ping metrics (gitlab-org/gitlab#397136 - closed)
syasonik
-
Update documentation related to self-monitoring... (gitlab-org/gitlab#394998 - closed)
rkadam3
-
Remove self_monitor_form.vue component and rela... (gitlab-org/gitlab#394992 - closed)
rkadam3
-
Remove usages of self-monitoring related code i... (gitlab-org/gitlab#394991 - closed)
rkadam3
-
Delete self monitoring project related services... (gitlab-org/gitlab#394989 - closed)
rkadam3
-
Delete database importers for self-monitoring p... (gitlab-org/gitlab#394987 - closed)
rkadam3
-
Delete self monitoring project workers and thei... (gitlab-org/gitlab#394986 - closed)
rkadam3
-
Service Desk config errors visible to non-admins (gitlab-org/gitlab#384530)
splattael
-
Service Desk: Attribute comment authorship for ... (gitlab-org/gitlab#226995 - closed)
rkadam3
%15.9 rollover:
Data from: GitLab REST API. Contains open issues which are in a prior milestone & assigned to a grouprespond engineer.
16.0 focus area distribution
44% typemaintenance | 22% typefeature | 22% typebug | 11% w/o type |
---|---|---|---|
50% w/o sub-type 25% maintenancepipelines 25% maintenancerefactor |
100% featureconsolidation | 100% w/o sub-type | 100% w/o sub-type |
44% w/o epic | 33% 16.0 Monitor Stage Removal (gitlab-org&7783) | 11% Ruby 3: Post-release tasks (gitlab-org&9635) | 11% Improve Respond group documentation (gitlab-org&7895) |
---|---|---|---|
75% w/o eng label 25% frontend |
67% w/o eng label 33% backend frontend |
100% w/o eng label | 100% w/o eng label |
End of week progress snapshot
~30% complete of 16.0 scheduled work
- 52% - of scheduled issues without an epic
- 25% - 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)
- 38% - 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 - 52% complete
Issue | Status | ~% Complete |
---|---|---|
Use delegated `Project#member?` instead of `Pr... (gitlab-org/gitlab#408201 - closed) Type: typemaintenance maintenancerefactor Domains: backend frontend documentation Possible action items required- check workflow label for accuracy - actual is workflowin dev, but there are open MRs |
@splattael No frontend assignee workflowin review Relevant MRs: (2) Reviewed/stalled MRs (1): gitlab-org/gitlab!118213 (merged) Merged MRs (1): gitlab-org/gitlab!117897 (merged) |
80% |
Wrong Content-Type of Service Desk `new_note` e... (gitlab-org/gitlab#404967 - closed) Type: typebug bugfunctional Domains: |
@msaleiko No grouprespond assignee workflowready for development Relevant MRs: (1) Draft MRs (1): gitlab-org/gitlab!118359 (merged) |
20% |
Service Desk: When editing an internal note, th... (gitlab-org/gitlab#399828) Type: typebug Domains: |
No assignee workflowready for development |
0% |
Monitor: Metrics Deprecation and Removal - 25% 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 - 38% complete
Contributions on: 95 merge_requests, 63 issues, 3
Contributions span from 2023-04-14 to 2023-04-22.
tristan.read focus areas
- Type: 79% typemaintenance, 21% typefeature
- Group: 34% groupsecurity policies, 11% grouprespond, 9% grouprunner, 9% grouppackage registry, 8% groupcontainer registry, 6% groupgitaly, 6% groupux paper cuts, 17% other (<3% each)
- Category: 26% Category:Security Policy Management, 9% ~"Category:Runner Fleet", 9% Category:Package Registry, 8% Category:Secrets Management, 8% Category:Incident Management, 8% Category:Container Registry, 32% other (<3% each)
- Work item: 87% ~"merge_requests", 13% issues
grouprespond contributions
merge_requests
- Draft: Add a Tag Name filter to the Incident : commented on (2), opened (1) issues
- Clean up presentation of items in incident high... (gitlab-org/gitlab#360009 - closed) : commented on (3)
other contributions
merge_requests
- Remove direct data manipulation from : accepted (6), commented on (22), approved (10)
- Fix lighthouse job and upgrade @gitlab/ui to : commented on (3), opened (1), approved (1) issues
- rspec-all frontend_fixtures as-if-foss sometime... (gitlab-org/gitlab#407588 - closed) : commented on (2), closed (1), opened (1)
psjakubowska focus areas
- Type: 61% typefeature, 37% typemaintenance, 1% other (<3% each)
- Group: 52% grouprespond, 36% groupanti-abuse, 7% groupcompliance, 3% ~"group::import", 1% other (<3% each)
- Category: 21% Category:Metrics, 18% Category:Service Desk, 10% Category:On-call Schedule Management, 7% Category:Audit Events, 3% Category:Importers, 40% other (<3% each)
- Work item: 87% ~"merge_requests", 13% issues
grouprespond contributions
merge_requests
- Introduce ff for deprecating Monitor Metrics : commented on (20), opened (3), approved (2), closed (2) issues
- Fix spec violations in spec/frontend/monitoring... (gitlab-org/gitlab#390979 - closed) : commented on (5), closed (2)
- Ops Showcase Presentation: Incident event tags (gitlab-org/ci-cd/section-showcases#14 - closed) : opened (1)
other contributions
merge_requests
- Resolve "Remove page-wide reload on audit : commented on (29), approved (2) issues
- Fix spec violations in spec/frontend/vue_shared... (gitlab-org/gitlab#398202 - closed) : closed (1)
splattael focus areas
- Type: 66% typemaintenance, 22% typefeature, 9% typebug, 4% other (<3% each)
- Group: 17% ~"group::ai-enablement", 15% grouprespond, 7% groupglobal search, 6% groupfoundations, 5% ~"group::import", 4% grouptenant scale, 4% groupcompliance, 3% groupproject management, 3% ~"group::incubation", 2% groupsource code, 34% other (<3% each)
- Category: 6% Category:Internationalization, 3% Category:Integrations, 3% Category:MLOps, 3% ~"Category:Projects", 2% Category:Source Code Management, 83% other (<3% each)
- Work item: 81% ~"merge_requests", 19% issues
grouprespond contributions
merge_requests
- Add RuboCop rule Gettext/StaticIdentifier : commented on (28), opened (9) issues
- Use delegated `Project#member?` instead of `Pr... (gitlab-org/gitlab#408201 - closed) : opened (1), commented on (2), closed (2)
other contributions
issues
- New Rubocop rule against sprintf/interpolation ... (gitlab-org/gitlab#408337 - closed) : commented on (26), opened (13), closed (2)
- Errors do not always show up (gitlab-org/opstrace/opstrace#2146 - closed) : commented on (3)
- 2023-04-20 Untriaged community merge requests r... (gitlab-org/quality/triage-reports#12087 - closed) : commented on (2)
- Remove permanently disabled rules (gitlab-org/ruby/gems/gitlab-styles#56) : commented on (1)
- "runsv rails-web" is sometimes not stopped/killed (gitlab-org/gitlab-development-kit#1798) : opened (1)
- An issue to be promoted to incident (splattael/mwps#23) : opened (1) merge_requests
- RSpec/UselessDynamicDefinition: Fix current : commented on (147), accepted (19), opened (1), approved (24)
- Make Suraj Tripathi a Backend Maintainer : approved (1)
syasonik focus areas
- Type: 62% typefeature, 14% typemaintenance, 24% other (<3% each)
- Group: 52% grouprespond, 14% groupproduct planning, 10% groupproject management, 24% other (<3% each)
- Category: 38% Category:Incident Management, 14% Category:Service Desk, 10% Category:Team Planning, 38% other (<3% each)
- Work item: 95% ~"merge_requests", 5% issues
grouprespond contributions
issues
- Remove Embed Grafana panels in Markdown (gitlab-org/gitlab#389477 - closed) : commented on (1) merge_requests
- Add quick action to add thread when opening : commented on (10)
other contributions
merge_requests
- Fix description updates for varied : accepted (2), opened (2), commented on (1)
- Delete vue_issues_dashboard feature flag : commented on (3), approved (2)
ck3g focus areas
- Type: 82% typemaintenance, 7% typefeature, 11% other (<3% each)
- Group: 68% grouprespond, 7% groupgeo, 25% other (<3% each)
- Category: 100% other (<3% each)
- Work item: 93% ~"merge_requests", 7% issues
grouprespond contributions
merge_requests
- Fix Layout/ArgumentAlignment offenses in : commented on (10), opened (9)
other contributions
merge_requests
- Revert "Merge branch : accepted (1), commented on (1), approved (1)
- Improve automated message for SUS-impacting : commented on (1)
- Make Suraj Tripathi a Backend Maintainer : approved (1), commented on (1), opened (1) issues
- Add shared examples for `admin mode` to ee geo ... (gitlab-org/gitlab#406571) : commented on (2)
rkadam3 focus areas
- Type: 74% typefeature, 13% typemaintenance, 11% typebug, 2% other (<3% each)
- Group: 62% grouprespond, 6% groupsecurity policies, 6% groupoptimize, 4% ~"group::integrations", 4% groupsource code, 4% groupstatic analysis, 13% other (<3% each)
- Category: 62% Category:Service Desk, 6% Category:Security Policy Management, 4% Category:Integrations, 4% Category:Source Code Management, 4% Category:SAST, 19% other (<3% each)
- Work item: 96% ~"merge_requests", 4% issues
grouprespond contributions
merge_requests
- Add attribution to external participant : commented on (27) issues
- Service Desk: Attribute comment authorship for ... (gitlab-org/gitlab#226995 - closed) : commented on (2)
other contributions
merge_requests
- Move Slack Options API to Core : commented on (7), approved (7), accepted (3)
- Make Suraj Tripathi a Backend Maintainer : approved (1)
francoisrose focus areas
- Type: 34% typeignore, 20% typefeature, 14% typebug, 11% typemaintenance, 20% other (<3% each)
- Group: 83% grouprespond, 3% groupfoundations, 3% groupproject management, 11% other (<3% each)
- Category: 26% Category:Incident Management, 17% Category:Service Desk, 3% Category:Portfolio Management, 3% Category:On-call Schedule Management, 3% Category:Team Planning, 49% other (<3% each)
- Work item: 91% issues, 9% other (<3% each)
grouprespond contributions
issues
- Monitor:Respond 16.0 Planning issue (#207 - closed) : commented on (8), closed (2)
- GitLab Service Desk JTBD (gitlab-org/gitlab#394968 - closed) : commented on (15)
- Feature flags requiring attention for group::re... (gitlab-org/quality/triage-reports#11848 - closed) : closed (2), commented on (2)
other contributions
issues
-
Upgrade httparty to 0.21 (gitlab-org/gitlab#389079 - closed) : commented on (3)
-
https://gitlab.com/francois-top-level-group/sub-group/service-desk : created project (3)
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
.