Prioritized Labels
  • IncidentActive
    Indicates that the incident labeled is active and ongoing.
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseConfig-Change
    Denotes a precipitating root cause of a configuration change (a change other than a feature flag being toggled)
    GitLab.com / GitLab Infrastructure Team / production
  • changescheduled
    Change plans that are ready and scheduled for execution. See https://about.gitlab.com/handbook/engineering/infrastructure/change-management/.
    GitLab.com / GitLab Infrastructure Team / production
  • incident
    GitLab.com / GitLab Infrastructure Team / production
  • oncall report
    GitLab.com / GitLab Infrastructure Team / production
  • review-requested
    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.
    GitLab.com / GitLab Infrastructure Team / production
  • IncidentMitigated
    Indicates that the incident has been mitigated, but immediate post-incident activity may be ongoing (monitoring, messaging, etc.)
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseExternal-Dependency
    Denotes a precipitating root cause resulting from the failure of a dependency external to GitLab, including various service providers.
    GitLab.com / GitLab Infrastructure Team / production
  • changein-progress
    This label indicates that a change from a Change Management issue is in progress.
    GitLab.com / GitLab Infrastructure Team / production
  • IncidentResolved
    Resolved - Indicates that SRE engagement with the incident has ended and GitLab.com is fully operational.
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseFeature-Flag
    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)
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseMalicious-Traffic
    Denotes a precipitating root cause of deliberate malicious activity targeted at GitLab or customers of GitLab (e.g. DDoS)
    GitLab.com / GitLab Infrastructure Team / production
  • IncidentReview-Scheduled
    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.
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseRelease-Compatibility
    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)
    GitLab.com / GitLab Infrastructure Team / production
  • IncidentReview-Completed
    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).
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseSPoF
    Denotes a precipitating root cause of the failure of a service or component which is an architectural SPoF (Single Point of Failure)
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseSaturation
    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)
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseSoftware-Change
    Denotes a precipitating root cause of a feature or other code change
    GitLab.com / GitLab Infrastructure Team / production
  • RootCauseSecurity
    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`
    GitLab.com / GitLab Infrastructure Team / production
  • Other Labels
  • (perceived) data loss
    An event that is seen as data loss from an external user
    GitLab.com / GitLab Infrastructure Team / production
  • 2021Q1 gitlab.com Latency Degradation
    GitLab.com
  • 22Q1-okr-fp&a
    GitLab.com
  • ABM 60 day
    Issues & Epics related to ABM 60 day launch plan (2019-12-01 to 2019-12-31)
    GitLab.com
  • ABM 90 day
    Issues & Epics related to ABM 90 day launch plan (2020-01-01 to 2020-01-31)
    GitLab.com
  • ABM FY22 Q3 Initiative
    GitLab.com
  • ABM FYI
    Issues that the Account Based team should be aware of but are not the DRI for
    GitLab.com
  • ABM Nomination
    Used to track accounts nominated for account based marketing
    GitLab.com
  • ABM campaign
    Issues & epics related to account based marketing campaigns
    GitLab.com
  • ABM tier 1
    all issues and epics related to ABM tier 1 campaigns
    GitLab.com
  • ABM tier 2
    All issues and epics related to ABM tier 2 campaigns
    GitLab.com
  • ABM tier 3
    All issues and epics related to ABM tier 3 campaigns
    GitLab.com
  • ABM-HB Update
    Handbook update for the ABM team.
    GitLab.com
  • AR-ApprovalNeeds Manager Approval
    Access Request pending Manager Approval
    GitLab.com
  • ARIn Queue
    Access Requests with assigned, approval labels, and ready to go
    GitLab.com
  • ARNeeds info
    this access request needs information to move forward
    GitLab.com
  • AROn hold
    Access Request pending licenses
    GitLab.com
  • ATAM
    Part of the Annual Total Addressable Market review
    GitLab.com
  • AWAWAW
    Personal tracking label for Alex W
    GitLab.com
  • AccessReviewClosed
    Completion of an access review
    GitLab.com