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 3,945
secauto|taskdocumentation
GitLab.com
Documentation of analysis results, techniques, components, features or products by SecAuto
secauto|taskimprovement
GitLab.com
Improvement or feature to be implemented in a SecAuto product or a supporting component initiated by an external team
secauto|taskincident
GitLab.com
Outages and related fire-fighting related to products and tooling by SecAuto
secauto|taskinfrastructure
GitLab.com
Work on non-product-related tooling internal to the Security Automation team
secauto|taskmaintenance
GitLab.com
Recurring or one-off work required to keep our products operative and usable
secauto|taskmanagement
GitLab.com
Signals that an issue and discussions contained therein are related to the management of the SecAuto team and ancillary topics
secauto|workflowawaiting-customer-input
GitLab.com
Signals that the SecAuto team is working on a task but is waiting for input from the customer.
secauto|workflowawaiting-manager-input
GitLab.com
Signals that a work unit and associated results require joint review by the SecAuto manager
secauto|workflowawaiting-team-input
GitLab.com
Signals that a work unit and associated results require review by SecAuto team
secauto|workflowblocked
GitLab.com
Signals that a work unit cannot be brought forward by SecAuto due to one or multiple blockers
secauto|workflowcancelled
GitLab.com
Signals that a work unit is no longer desired and hence shall not be delivered by SecAuto
secauto|workflowdone
GitLab.com
Signals that a work unit has been both delivered by SecAuto and accepted by the final customer
secauto|workflowin-progress
GitLab.com
Signals that a work unit is in-progress and to be delivered by SecAuto
secauto|workflownew
GitLab.com
Signals that this is a new potential task for the SecAuto team to triage, prioritize and if accepted execute on
secauto|workflowready
GitLab.com
Signals that a work unit has been triaged, properly scoped and is ready to be worked on by SecAuto
seccomp workflowblocked
GitLab.com
Issues that are blocked and need a resolution plan or escalation. Move to ~"seccomp workflow::in progress" once unblocked.
seccomp workflowcancelled
GitLab.com
Issue closed because the work was cancelled because it was no longer needed or relevant.