Monitor:Respond Weekly Update - W12 - Mar-20-2023
< previous update | next update > |
---|
Highlights
- @kbychu hosted the first Service Desk Product Office Hours, where he described both his short-term and long-term thinking for the category (Recording)
- We're building confidence in the timely removals scheduled for %16.0.
- @rkadam3 opened all necessary MRs to prepare for the removal of Self-Monitoring.
- @psjakubowska and @tristan.read are tag-teaming the preparation for the removal of Metrics.
- @psjakubowska attended an accessibility conference asynchronously, and shared her takeaways here: axe-con 2023 & 2022.
-
@splattael took a bias for action and made sure the
declarative-policy
gem now has maintainers (including himself). - @ck3g made several contributions to the GitLab CLI, with a long-term goal of supporting Incident Management via the CLI.
- @syasonik is actively making François's life easier by improving the generation of these weekly updates.
grouprespond in %15.10 = 66%
Say Do ratio for- Say = 3 goals = goals committed to by the team at the start of the milestone, see plan goals for the milestone.
- Do = 2 goals = goals which were achieved during the milestone.
-
✅ Enable Incident Tags for self-managed users - the feature is enabled, some FF cleanup is left. -
❌ Prepare for %16.0 removals - moved to %15.11. -
✅ Pave the way for grouprespond to start work on Category:Service Desk - Service Desk issues were identified/planned for 15.11, as well as a tech breakdown.
-
Notes on this calculation
At GitLab, Say Do ratios are typically based on issues labeled with Deliverable. This practice is not in place in grouprespond. Instead, we calculate the Say Do ratio by looking at the goals/epics we committed to in the plan description.
See this thread for the background on this methodology.
Background
Reporting on this Performance Indicator is part of an Ops Objective (Establish a consistent team capacity model in order to improve our ability to plan and prioritize) and Key Result (All teams report consistently on Say Do Ratios).
Handbook: https://about.gitlab.com/handbook/engineering/metrics/sec/secure/#say-do-ratios
Progress overview
~38% complete of 15.11 scheduled work
- 16% - of scheduled issues from epic: Monitor: Metrics Deprecation and Removal (gitlab-org&10107)
- 79% - of scheduled issues without an epic
- 32% - of scheduled issues from epic: Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed)
- 0% - of scheduled issues from epic: Incident Tag MVC (gitlab-org&8741)
- 25% - of scheduled issues from epic: Slack workflow service desk ticket creation (gitlab-org&10041 - 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...
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 |
Monitor: Metrics Deprecation and Removal - 16% complete
Standalone issues - 79% complete
Engineering Transition issue for Service Desk to Monitor - 32% complete
Issue | Status | ~% Complete |
---|---|---|
Service Desk: update ownership of feature flags (gitlab-org/gitlab#398164 - closed) Type: typemaintenance maintenancerefactor Domains: |
@francoisrose workflowverification |
95% |
Service Desk: update ownership of metrics (gitlab-org/gitlab#398163 - closed) Type: typemaintenance maintenancerefactor Domains: backend frontend Possible action items required- check workflow label for accuracy - workflow label is absent |
No assignee workflowready for development |
0% |
Incident Tag MVC - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Remove references to the `incident_event_tags` ... (gitlab-org/gitlab#398130 - closed) Type: typemaintenance Domains: backend frontend Possible action items required- check for missing subtype label |
No assignee workflowready for development |
0% |
Slack workflow service desk ticket creation - 25% complete
Issue | Status | ~% Complete |
---|---|---|
Technical Breakdown: Slack workflow service des... (#214 - closed) Type: typefeature Domains: |
@rkadam3 workflowin dev |
25% |
Monitor:Self-Monitoring Deprecation and Removal - 38% complete
This week: activity
Contributions on: 87 merge_requests, 92 issues, 3 epics
Contributions span from 2023-03-17 to 2023-03-25.
tristan.read focus areas
- Type: 64% typemaintenance, 30% typefeature, 7% typeignore
- Group: 23% grouprespond, 11% groupfoundations, 11% groupux paper cuts, 9% groupacquisition, 9% groupsource code, 7% ~"group::integrations", 30% other
- Category: 14% Category:Incident Management, 11% Category:Navigation & Settings, 9% Category:Source Code Management, 7% Category:Integrations, 2% Category:GDK, 2% Category:On-call Schedule Management, 55% other
- Work item: 80% ~"merge_requests", 20% issues
grouprespond contributions
merge_requests
- Draft: Add a Tag Name filter to the Incident : commented on (1)
- Add suggestion to retain service desk config : commented on (1) issues
- Monitor:Respond 15.11 Planning issue (#206 - closed) : commented on (3)
- [Feature flag] Rollout of `incident_event_tags` (gitlab-org/gitlab#387647 - closed) : commented on (4), opened (1)
other contributions
merge_requests
- Update dependency @gitlab/ui to v58.4.0 : accepted (4), approved (4), commented on (4)
- Remove left over invite_members_for_task : accepted (4), commented on (12), approved (5) issues
- Docs feedback: Consistent onboarding issues wit... (gitlab-org/gitlab#26115 - closed) : commented on (1)
psjakubowska focus areas
- Type: 77% typemaintenance, 7% typefeature, 3% typeignore, 13% other
- Group: 65% grouprespond, 17% groupux paper cuts, 5% groupfoundations, 3% groupproduct planning, 10% other
- Category: 35% Category:On-call Schedule Management, 7% Category:Incident Management, 3% Category:Metrics, 3% Category:Portfolio Management, 52% other
- Work item: 60% ~"merge_requests", 40% issues
grouprespond contributions
issues
- [Feature flag] Rollout of `remove_monitor_metrics` (gitlab-org/gitlab#399248) : opened (5), closed (3), commented on (10)
- Monitor:Respond 15.11 Planning issue (#206 - closed) : commented on (3) merge_requests
- Draft: Resolve "Metrics: hide deprecated : opened (2), commented on (15), closed (1)
other contributions
issues
- [Feature flag] Rollout of `remove_monitor_metrics` (gitlab-org/gitlab#399247 - closed) : closed (1), opened (1), commented on (1) merge_requests
- Issues list: change status to use badge : commented on (13), approved (3), opened (1)
- fix(GlDisclosureDropdown): Keep focus on : commented on (1)
splattael focus areas
- Type: 74% typemaintenance, 12% typefeature, 14% other
- Group: 45% grouprespond, 7% groupglobal search, 6% groupcode review, 6% ~"group::import", 5% ~"group::product intelligence", 3% ~"group::authentication and authorization", 3% groupobservability, 3% groupfoundations, 2% groupproject management, 2% grouppipeline security, 19% other
- Category: 13% Category:Service Desk, 8% Category:Internationalization, 2% Category:Metrics, 77% other
- Work item: 73% ~"merge_requests", 27% issues
grouprespond contributions
merge_requests
- Use benchmark-ips to measure performance : commented on (8)
- Quarantine flaky test for issues form : accepted (1), commented on (48), approved (1), opened (4) issues
- Move member roles factories to EE (gitlab-org/gitlab#397700 - closed) : commented on (4), opened (1)
other contributions
issues
- Thursday 2023-03-23 17:13 UTC - `gitlab-org/git... (gitlab-org/quality/engineering-productivity/master-broken-incidents#1236 - closed) : commented on (5), closed (1)
- RSpec: `aggregate_failures` tags are misspelled (gitlab-org/gitlab#396356 - closed) : commented on (19), closed (5), opened (2)
- This project has no assignments on Engineering ... (gitlab-org/ruby/gems/declarative-policy#27 - closed) : closed (1), commented on (1)
- New GitLab token scopes for Observability (gitlab-org/opstrace/opstrace#2086 - closed) : commented on (1) merge_requests
-
Add
approved
filter to merge requests api : accepted (6), commented on (30), approved (9) - Disable RSpec/MultipleMemoizedHelpers : commented on (2)
- Add reviewers and maintainers for GitLab : commented on (1)
syasonik focus areas
- Type: 35% typemaintenance, 17% typefeature, 8% typeignore, 6% typebug, 33% other
- Group: 54% grouprespond, 6% groupthreat insights, 4% grouptenant scale, 4% groupoptimize, 31% other
- Category: 23% Category:Metrics, 8% Category:Incident Management, 6% Category:Vulnerability Management, 63% other
- Work item: 54% ~"merge_requests", 44% issues, 2% epics
grouprespond contributions
issues
- Monitor:Respond Weekly Update - W12 - Mar-20-2023 (#217 - closed) : commented on (4), closed (2)
- [Feature flag] Rollout of `incident_timeline_ev... (gitlab-org/gitlab#369416) : commented on (1), opened (9), closed (1) merge_requests
- Refactor to accommodate using milestone : commented on (3), accepted (1), opened (1)
- Enable incident declare slack command in open : commented on (3) epics
- Monitor: Metrics Deprecation and Removal (gitlab-org&10107) : opened (1)
other contributions
merge_requests
- Update current weekly update issue & create : commented on (3), accepted (1), opened (1)
- Remove long-running transaction while : commented on (8), approved (5) issues
- Monitor:Respond Weekly Update - W13 - Mar-27-2023 (syasonik/ten-things-to-know-about-gitlab-ci#12) : opened (2)
- Mistake issue (gitlab-org/gitlab#397143 - closed) : closed (1), opened (1)
ck3g focus areas
- Type: 47% typemaintenance, 35% typefeature, 12% typebug, 6% other
- Group: 43% grouprespond, 14% grouptenant scale, 8% groupacquisition, 8% groupdatabase, 6% groupthreat insights, 6% ~"group::authentication and authorization", 4% grouppackage registry, 4% groupcode review, 4% grouppipeline execution, 4% other
- Category: 16% Category:GitLab CLI, 14% Category:Incident Management, 14% Category:User Profile, 8% Category:Database, 4% Category:Package Registry, 45% other
- Work item: 86% ~"merge_requests", 14% issues
grouprespond contributions
merge_requests
- Document Incident Timeline Events from Labels : commented on (6), opened (3), accepted (2), approved (2)
- refactor(test): replace os.Setenv with : commented on (2), opened (2) issues
- Improve slow tests in ./spec/features/issues/in... (gitlab-org/gitlab#365774 - closed) : commented on (2), closed (1)
- Replace os.Setenv with t.Setenv in tests (gitlab-org/cli#1282 - closed) : opened (2)
other contributions
issues
- API changes should be reviewed by experts (gitlab-org/gitlab#393119) : commented on (1)
- glab ci view render log with black character ov... (gitlab-org/cli#1281 - closed) : commented on (1) merge_requests
- Drop packages_events table : commented on (14), approved (7), accepted (4)
- Add Rodrigo Tomonari as backend maintainer - : approved (1)
- fix(color): fix gray color for 256 color : commented on (1)
rkadam3 focus areas
- Type: 43% typemaintenance, 30% typefeature, 13% typeignore, 13% other
- Group: 57% grouprespond, 13% grouptenant scale, 13% groupproduct planning, 13% ~"group::integrations", 4% other
- Category: 4% Category:Service Desk, 4% Category:Incident Management, 91% other
- Work item: 74% ~"merge_requests", 22% issues, 4% epics
grouprespond contributions
issues
- Technical Breakdown: Slack workflow service des... (#214 - closed) : commented on (3), closed (1)
- Add a pagerduty icon as an option for relating ... (gitlab-org/gitlab#393261) : commented on (1) epics
- Monitor:Self-Monitoring Deprecation and Removal (gitlab-org&10030 - closed) : commented on (1) merge_requests
- Draft: Misc removals related to self : opened (5), commented on (2)
other contributions
merge_requests
- Let TableLocker return hash with results : accepted (2), opened (1), commented on (4), approved (3)
francoisrose focus areas
- Type: 49% typefeature, 22% typemaintenance, 10% typebug, 5% typeignore, 14% other
- Group: 92% grouprespond, 8% other
- Category: 53% Category:Incident Management, 20% Category:Service Desk, 27% other
- Work item: 83% issues, 14% ~"merge_requests", 3% epics
grouprespond contributions
epics
- Monitor: Metrics Deprecation and Removal (gitlab-org&10107) : commented on (1)
- Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed) : opened (1) issues
- Failure in ee/browser_ui/8_monitor/alert_manage... (gitlab-org/gitlab#397133 - closed) : commented on (34), closed (4), opened (6)
- Monitor:Respond 15.10 Planning issue (#199 - closed) : closed (2), commented on (1) merge_requests
- Enable incident declare slack command in open : commented on (3), approved (1)
- Refactor to accommodate using milestone : commented on (1)
other contributions
merge_requests
- Respond: replace labels table with a bullet : accepted (1), opened (2) issues
- Docs feedback: Consistent onboarding issues wit... (gitlab-org/gitlab#26115 - closed) : commented on (1), closed (1)
Data from: Scraped from activity page for each user. Activities which don't support labels are mostly ignored.
Next week: capacity
73% (80% of frontend, 70% of backend)
-
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
8 Rollover issues from %15.9, %15.10
%15.9 rollover:
-
Add colors for user tokens in escalation policy... (gitlab-org/gitlab#335680 - closed)
psjakubowska
-
Upgrade httparty to 0.21 (gitlab-org/gitlab#389079 - closed)
splattael
-
Phase 1: Add `/slack <channel>` quick action to... (gitlab-org/gitlab#345063)
syasonik
-
Phase 1: Add `/gitlab incident timeline <text>`... (gitlab-org/gitlab#365366)
ck3g
-
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 retrieved via GitLab REST API. Open issues assigned to a grouprespond engineer, in prior milestone.
🔗 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
.