Monitor:Respond Weekly Update - W14 - Apr-03-2023
< previous update | next update > |
---|
Highlights
- Decision: Slack workflow service desk ticket creation (gitlab-org&10041 - closed) was closed & work stopped to better align our efforts with the IT Ops team goals and most likely customers
- Escalation: The CES team's service desk broke for multiple days due to an email client config problem. We learned we've got some visibility gaps in both our own troubleshooting, and in tools to enable users to troubleshoot.
Going into the week
Capacity: 73% (40% of frontend, 90% of backend)
For the week of Monday, 2023-04-03.
-
frontend: max of 2 engineers, 5 days in week
4(days) = 10(days) - 6(PTO)
-
backend: max of 4 engineers, 5 days in week
18(days) = 20(days) - 2(PTO)
Data from: Monitor:Respond Group Calendar, via Google App Scripts
1 Rollover issues from %15.9
%15.9 rollover:
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 |
---|---|
44% maintenanceremoval 39% 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% Engineering Transition issue for Service Desk t... (gitlab-org&10127 - closed) | 15% w/o epic | 10% Monitor:Self-Monitoring Deprecation and Removal (gitlab-org&10030 - 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 |
83% w/o eng label 17% backend frontend |
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
~56% complete of 15.11 scheduled work
- 23% - of scheduled issues from epic: Monitor: Metrics Deprecation and Removal (gitlab-org&10107)
- 94% - of scheduled issues without an epic
- 43% - 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)
- 100% - 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 - 23% complete
Standalone issues - 94% complete
Engineering Transition issue for Service Desk to Monitor - 43% 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 workflowproduction Relevant MRs: (1) Merged MRs (1): gitlab-org/gitlab!115834 (merged) |
100% |
Slack workflow service desk ticket creation - 100% complete
Issue | Status | ~% Complete |
---|---|---|
Technical Breakdown: Slack workflow service des... (#214 - closed) Type: typefeature Domains: backend Possible action items required- check for missing subtype label |
@rkadam3 workflowin review Relevant MRs: (1) Merged MRs (1): gitlab-org/gitlab!105960 (merged) |
100% |
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: 64 merge_requests, 44 issues, 2 epics
Contributions span from 2023-03-31 to 2023-04-08.
tristan.read focus areas
- Type: 70% typefeature, 30% typemaintenance
- Group: 72% grouprespond, 13% groupcode review, 9% groupfoundations, 7% other (<3% each)
- Category: 30% Category:Service Desk, 2% Category:Incident Management, 67% other (<3% each)
- Work item: 98% ~"merge_requests", 2% issues
grouprespond contributions
merge_requests
- Adds service desk custom email verification : commented on (31), approved (1) issues
- Remove Embed Grafana panels in Markdown (gitlab-org/gitlab#389477 - closed) : commented on (1)
other contributions
merge_requests
- Replace sticky-top-position mixin with header : accepted (2), commented on (6), approved (2)
- Update dependency @gitlab/ui to v59.3.1 : accepted (1), approved (1), commented on (1)
splattael focus areas
- Type: 68% typemaintenance, 18% typefeature, 9% typebug, 5% other (<3% each)
- Group: 22% grouprespond, 20% ~"group::import", 11% groupobservability, 11% groupcompliance, 11% groupscalability, 5% groupsource code, 3% groupfoundations, 18% other (<3% each)
- Category: 13% Category:Internationalization, 11% Category:Audit Events, 9% Category:Error Tracking, 6% Category:Importers, 5% Category:Source Code Management, 56% other (<3% each)
- Work item: 79% ~"merge_requests", 20% issues, 1% other (<3% each)
grouprespond contributions
merge_requests
- Stub member access level in specs : commented on (22), opened (4), approved (1)
- Upgrade gitlab-styles to 10.0 : commented on (6), closed (1) issues
- ArgumentError: wrong number of arguments (given... (gitlab-org/gitlab#394848 - closed) : commented on (3)
other contributions
issues
- Undefined method default_syntax_highlighting_theme (gitlab-org/gitlab#402970 - closed) : commented on (22), opened (5), closed (3)
- Evaluate existing GitLab Integrated ErrorTracki... (gitlab-org/opstrace/opstrace-ui#252 - closed) : commented on (1)
- Trainee BE maintainer (GitLab) - Dzmitry Meshch... (gitlab-com/www-gitlab-com#14356 - closed) : commented on (1) merge_requests
- Add default option for Syntax Highlighting : commented on (86), accepted (5), approved (9)
- Make Laura Montemayor a backend maintainer : approved (1) epics
- Ruby 3.1 (gitlab-org&10034) : commented on (1)
syasonik focus areas
- Type: 56% typefeature, 25% typemaintenance, 6% typeignore, 13% other (<3% each)
- Group: 69% grouprespond, 19% groupacquisition, 6% groupproject management, 6% other (<3% each)
- Category: 44% Category:Incident Management, 13% Category:Metrics, 44% other (<3% each)
- Work item: 81% ~"merge_requests", 19% issues
grouprespond contributions
merge_requests
- Add alternate technical breakdown for : accepted (1)
- Draft: Remove metrics category from service : opened (2), commented on (6) issues
- Monitor:Respond Weekly Update - W14 - Apr-03-2023 (#226 - closed) : commented on (1)
- Remove Embed Grafana panels in Markdown (gitlab-org/gitlab#389477 - closed) : commented on (1)
other contributions
merge_requests
- Add reveal-conceal password option : commented on (3), approved (1) issues
- Data issues in weekly update activity/completion (#229) : opened (1)
ck3g focus areas
- Type: 58% typefeature, 37% typemaintenance, 5% other (<3% each)
- Group: 52% grouprespond, 6% groupthreat insights, 5% groupproject management, 5% ~"group::incubation", 5% grouppackage registry, 5% groupsource code, 5% groupproduct analytics, 3% grouptenant scale, 2% ~"group::integrations", 2% groupsecurity policies, 2% groupfoundations, 2% groupglobal search, 6% other (<3% each)
- Category: 12% Category:GitLab CLI, 5% Category:Issue Tracking, 5% Category:Service Desk, 5% Category:Vulnerability Management, 5% Category:Source Code Management, 5% ~"Category:Product Analytics", 3% Category:User Profile, 3% Category:Package Registry, 2% Category:Security Policy Management, 2% Category:Global Search, 2% Category:Incident Management, 51% other (<3% each)
- Work item: 90% ~"merge_requests", 10% issues
grouprespond contributions
merge_requests
- Improve rendering of HTML-only emails in : commented on (19), approved (4), opened (8)
-
feat(incident): add
incident close
command : commented on (8), opened (1) issues - Remove references to the `incident_event_tags` ... (gitlab-org/gitlab#398130 - closed) : commented on (3), closed (2)
other contributions
merge_requests
- Remove unused ee_ci_job_artifact Factory : approved (11), commented on (22), opened (1), accepted (1)
- Make Laura Montemayor a backend maintainer : approved (1)
- Support environment variable substitution in : commented on (1) issues
- Follow-up from "Scope iteration report to subgr... (gitlab-org/gitlab#320814 - closed) : commented on (1), closed (1)
- feat(docs): display a command aliases in docs (gitlab-org/cli#1299 - closed) : opened (1)
- Test incident (cli-automated-testing/test#2 - closed) : opened (1)
rkadam3 focus areas
- Type: 67% typefeature, 25% typemaintenance, 8% other (<3% each)
- Group: 75% grouprespond, 11% groupoptimize, 5% ~"group::product intelligence", 5% groupacquisition, 3% other (<3% each)
- Category: 41% Category:Service Desk, 11% Category:Incident Management, 5% Category:Onboarding, 43% other (<3% each)
- Work item: 54% ~"merge_requests", 46% issues
grouprespond contributions
issues
- Service Desk: Attribute comment authorship for ... (gitlab-org/gitlab#226995 - closed) : commented on (13)
- Technical Breakdown: Slack workflow service des... (#214 - closed) : commented on (14)
- Ops Showcase Presentation: GitLab Incident mana... (gitlab-org/ci-cd/section-showcases#12 - closed) : commented on (1) merge_requests
- Adds Service Desk custom email verification : commented on (15), approved (1), closed (1), opened (1)
other contributions
merge_requests
- Drop gitlab-mail_room gem update in : approved (1)
- Remove empty product_category from metric : accepted (1), commented on (9), approved (3)
- Make Laura Montemayor a backend maintainer : approved (1)
francoisrose focus areas
- Type: 29% typemaintenance, 12% typefeature, 6% typeignore, 53% other (<3% each)
- Group: 59% grouprespond, 41% other (<3% each)
- Category: 41% Category:Service Desk, 6% Category:Metrics, 53% other (<3% each)
- Work item: 94% issues, 6% epics
grouprespond contributions
issues
- Monitor:Respond Weekly Update - W13 - Mar-27-2023 (#225 - closed) : closed (1), commented on (2), opened (1)
- Ops Showcase Presentation: GitLab Incident mana... (gitlab-org/ci-cd/section-showcases#12 - closed) : opened (1)
- Service Desk: update ownership of feature flags (gitlab-org/gitlab#398164 - closed) : commented on (3), closed (2)
other contributions
issues
- https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/17538+ : commented on (1)
- PM Coverage for Kevin Chu from 2023-03-29 to 20... (gitlab-com/Product#5591 - closed) : commented on (1)
- CES: Service Desk Dogfooding (gitlab-org/gitlab#403602 - moved) : closed (1), opened (1)
- Service Desk dogfooding example: Account Deleti... (#227) : opened (1), commented on (1) epics
- Create incidents through Slack (gitlab-org&8805) : 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
.