Document Incident Reporting Process for Analytics Instrumentation Group

Why is this change being made?

Relates to: gitlab-org/analytics-section/analytics-instrumentation/internal#662 (closed)

The incidents that arise within the Analytics Instrumentation domain could impact the quality of metrics reported, including business critical metrics such as xMAUs. This in-turn affects the quality of business decisions made using these metrics. The current incident process in the handbook addresses customer facing incidents and since a major part of the scope of the Analytics Instrumentation domain is internal facing, incidents that have a significant impact on business metrics don't always get the necessary attention and the required urgency for quick resolution (e.g., faster reviews and so on). More context here.

The goal of this MR is to publish a team specific incident reporting process aimed at getting the necessary attention and urgency to resolve high impact incidents quickly

Author Checklist

• 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 changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---