Skip to content

Add page documenting each tier 2 rotation

Devin Sylvarequested to merge
devin/tier2-escalations into main

We need a central place to document which Tier 2 rotations are currently active, and what kind of escalations they are available to handle. This first iteration documents the 4 Tier 2 services that we currently have. The expectation is that it will grow and be refined as we add more Tier 2 rotations.

We currently have:

  • Gitaly
  • Database Operations
  • AI Gateway and Assistant
  • DevOps Rails

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

Commits

  • Add page documenting each tier 2 rotation
Edited by Devin Sylva

Merge request reports