Prioritized labels 20
Drag to reorder prioritized labels and change their relative priority.
DBRE Headroom
GitLab.com / GitLab Infrastructure Team / Production
One off label to track database headroom work for the DBRE team
RootCauseConfig-Change
GitLab.com / GitLab Infrastructure Team / Production
Denotes a precipitating root cause of a configuration change (a change other than a feature flag being toggled)
changescheduled
GitLab.com / GitLab Infrastructure Team / Production
Change plans that are ready and scheduled for execution. See https://about.gitlab.com/handbook/engineering/infrastructure/change-management/.
incident
GitLab.com / GitLab Infrastructure Team / Production
See our definition of an incident at https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/incident-management/.
IncidentActive
GitLab.com / GitLab Infrastructure Team / Production
Indicates that the incident labeled is active and ongoing.
review-requested
GitLab.com / GitLab Infrastructure Team / Production
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.
IncidentMitigated
GitLab.com / GitLab Infrastructure Team / Production
Indicates that the incident has been mitigated, but immediate post-incident activity may be ongoing (monitoring, messaging, etc.)
RootCauseExternal-Dependency
GitLab.com / GitLab Infrastructure Team / Production
Denotes a precipitating root cause resulting from the failure of a dependency external to GitLab, including various service providers.
changein-progress
GitLab.com / GitLab Infrastructure Team / Production
This label indicates that a change from a Change Management issue is in progress.
IncidentResolved
GitLab.com / GitLab Infrastructure Team / Production
Resolved - Indicates that SRE engagement with the incident has ended and GitLab.com is fully operational.
RootCauseFeature-Flag
GitLab.com / GitLab Infrastructure Team / Production
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)
RootCauseMalicious-Traffic
GitLab.com / GitLab Infrastructure Team / Production
Denotes a precipitating root cause of deliberate malicious activity targeted at GitLab or customers of GitLab (e.g. DDoS)
IncidentReview-Scheduled
GitLab.com / GitLab Infrastructure Team / Production
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.
RootCauseRelease-Compatibility
GitLab.com / GitLab Infrastructure Team / Production
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)
IncidentReview-Completed
GitLab.com / GitLab Infrastructure Team / Production
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).
RootCauseSPoF
GitLab.com / GitLab Infrastructure Team / Production
Denotes a precipitating root cause of the failure of a service or component which is an architectural SPoF (Single Point of Failure)
RootCauseSaturation
GitLab.com / GitLab Infrastructure Team / Production
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)
RootCauseSoftware-Change
GitLab.com / GitLab Infrastructure Team / Production
Denotes a precipitating root cause of a feature or other code change
RootCauseSecurity
GitLab.com / GitLab Infrastructure Team / Production
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`
Labels 4,100
release toil
GitLab.com / GitLab Infrastructure Team
Issues related to reducing the amount of toil surrounding releases
release tooling
GitLab.com / GitLab Infrastructure Team
Issues related to tooling needed for all types of GitLab releases
release-blocker
GitLab.com
An issue or a task blocking a release, either auto_deploy or customer packages
release-tools single pipeline
GitLab.com
Issues related to creating a single release-tools pipeline that coordinates other release pipelines gitlab-com/gl-infra&154
release-tools single pipelinephase 2
GitLab.com / GitLab Infrastructure Team
Issues associated to Single Pipeline - Phase 2 &361
renovate-upgrade-requires-integration-test
GitLab.com / GitLab Infrastructure Team
This renovate dependency upgrade change should undergo full integration testing before being merged.
https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/blob/main/engineering/dependency-upgrades-with-renovate.md
requires commented manager approval
GitLab.com / GitLab Infrastructure Team / Production
requires production access
GitLab.com / GitLab Infrastructure Team / Production
Whenever an action requires to jump into production
requires-environment-upgrade-test
GitLab.com / GitLab Infrastructure Team
This renovate upgrade should be applied to an existing environment as part of it's testing, so that the upgrade migration process can be validated.
https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/blob/main/engineering/dependency-upgrades-with-renovate.md
research
GitLab.com / GitLab Infrastructure Team
Investigation or analysis issue to gather information for use on other issues