One off label to track database headroom work for the DBRE team

Denotes a precipitating root cause of a configuration change (a change other than a feature flag being toggled)

Change plans that are ready and scheduled for execution. See https://about.gitlab.com/handbook/engineering/infrastructure/change-management/.

See our definition of an incident at https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/incident-management/.

Indicates that the incident labeled is active and ongoing.

Indicates that that the incident would benefit from undergoing additional review. All S1 incidents are required to have a review. Additionally, anyone including the EOC can request an incident review on any severity issue. Although the review will help to derive corrective actions, it is expected that corrective actions are filled whether or not a review is requested. If an incident does not have any corrective actions, this is probably a good reason to request a review for additional discussion.

Indicates that the incident has been mitigated, but immediate post-incident activity may be ongoing (monitoring, messaging, etc.)

Denotes a precipitating root cause resulting from the failure of a dependency external to GitLab, including various service providers.

This label indicates that a change from a Change Management issue is in progress.

Resolved - Indicates that SRE engagement with the incident has ended and GitLab.com is fully operational.

Denotes a precipitating root cause of a feature flag toggled in some way (off or on or a new percentage or target was chosen for the feature flag)

Denotes a precipitating root cause of deliberate malicious activity targeted at GitLab or customers of GitLab (e.g. DDoS)

Review-Scheduled Indicates that an incident review writeup is required (S1/S2) or requested and that the review has been added to the agenda for an upcoming review meeting.

Denotes a precipitating root cause of forward- or backwards-compatibility issues between subsequent releases of the software running concurrently, and sharing state, in a single environment (ie, Canary and Main stage releases)

Review-Completed Indicates that an incident review writeup has been completed (the review was discussed in a review meeting and all notes from that meeting have been added to the review write-up).

Denotes a precipitating root cause of the failure of a service or component which is an architectural SPoF (Single Point of Failure)

Denotes a precipitating root cause of a failure resulting from a service or component which failed to scale in response to increasing demand (whether or not it was expected)

Denotes a precipitating root cause of a feature or other code change

an incident where the SIRT team was engaged, generally via a request originating from the SIRT team or in a situation where Reliability has paged SIRT to assist in the mitigation of an incident not caused by `~RootCause::Malicious-Traffic`