Update support workflow for Dedicated emergency
Why is this change being made?
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.Please add the details saying why, not just what in this section. Example:
We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.
This change adds explicit guidance about setting investigation update timeframes with customers.
This change addresses post-incident feedback from a Dedicated customer's ASE (eligible_pink_eel
) regarding incident communication (ZD 596056). In the ticket, the customer specifically also asked:
Thank you for the follow ups. Can I check what is the next checkpoint on this issue?
We already have clear timeframe guidelines for CMOCs and we should to extend this practice to Dedicated incidents. This is important because:
- Customers may not be aware of ongoing investigation progress
- They need to update their internal stakeholders
- Clear update timeframes help set expectations and allow our Support Engineers and Dedicated SREs to focus on investigation
I think proper impact assessment needs to be baked into the SRE incident management process to establish CMOC-like timeframe guidelines, so I left the update frequency assessment to the Support Engineer handling the incident ticket.
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Update file dedicated.md
Merge request reports
Activity
added HandbookContent label
assigned to @dkua1
requested review from @bcarranza, @ahergenhan, and @weimeng-gtlb
- Resolved by Daphne Kua
@bcarranza @ahergenhan @weimeng-gtlb Can I get your thoughts on this MR?
started a merge train
mentioned in commit 247b2b98