19 March

• Developed story telling slide deck to demonstrate progression to proposed state - this is a mental map change, not a behaviour or action change, though those will come
• Have received feedback that I need to ensure there are some concrete examples or explanations associate with this before launching.
• Seeking further feedback before going deeper on the content

The training module is unrelated to the sessions we had with LHC last year. The module is one that Lyle set up, and I do think it's worth being maintained. We would only do additional sessions with LHC if we proposed it and got budget to do it.

Worth noting that forms_processor supports more than just SWIR - there are a bunch of forms it serves - and it doesn't have a maintainer. And I'm not sure if the other forms in it (STAR!) are still served from there or not.

Why is this change being made?

From RFC: Process for Cross-Referencing Self-Managed Performance Issues with GitLab.com and GitLab Dedicated:

When customers report performance issues on self-managed instances, Support Engineers often investigate these issues in isolation without checking if similar problems have been identified or resolved in GitLab.com or GitLab Dedicated environments.

This workflow will help to investigate and drive resolution of database-related performance issues reported by customers through collaboration with Engineering teams.

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
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• 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

• Add new workflow for investigating DB perf issues

---

Deleted prior layers. March 2026 onward is the only layer in the schedule now.