Content last updated 2025-04-28

サポート用語集

サポート用語集には、サポート関連の頭字語と用語の定義および説明が含まれています。

サポート用語集

サポート用語集には、サポート関連の頭字語と用語の定義および説明が含まれています。エントリはアルファベット順にソートされており、可能な限り定義のソースへのリンクを記載するか、ソースを含めるべきです。

この用語集は この Issue からインスピレーションを得ており、GitLab サポート固有の可能性のある用語の定義を提供することを目的としています。

定義が欠けているドキュメントを読んでいてこのページに来た場合は、頭字語と頭文字語 スタイルに揃えて、頭字語の展開で元のページを更新してください。

AcronymFull nameMore information
AIGWAI gateway

See AI gateway docs page.

AMERAmericas

See “AMER” in List of country groupings on Wikipedia.

APACAsia-Pacific

Asia-Pacific on Wikipedia.

AQCActive Queue Carry

Experimental: AMER is exploring a metric called Active Queue Carry, which is the sum of tickets currently assigned to an engineer that are open, pending, solved, and on-hold. Tickets stay in a solved state for 7 days, so Active Queue Carry represents the most recent solved work.

ARRAnnual Recurring Revenue

See ARR in Sales Term Glossary.

ASEAssigned Support Engineer

Customers can subscribe to our assigned support engineer service which allocates them a named support engineer. You can read more about this role in the handbook.

BBMBatched Background Migrations

See Batched Background Migration docs page.

CEOCCustomer Emergencies On-Call

How to Perform Customer Emergencies Duties

CES
  • Customer Effort Score
  • Candidate Experience Specialist

In the support context, customer effort score is an approach to measuring customer satisfaction. In the wider GitLab context, we also have candidate experience specialists who are part of our recruiting team.

CMOCCommunications Manager On-Call

Support is responsible for keeping customers informed in support of our incident response process when there is an active incident on gitlab.com. The role has several responsibilities.

CSCustomer Success

Often used to refer to Customer Success team.

CSATCustomer Satisfaction Score

See Customer Satisfaction Surveys.

CSMCustomer Success Manager

CSMs are accountable for customer adoption, measurable outcomes, customer satisfaction, and creating true customer advocacy. You can read more here

CXCustomer Experience

See CX in Customer Experience page.

DAPDuo Agent Platform

See Duo GitLab Agent Platform docs page.

DASTDynamic Application Security Testing

A security testing method that tests running applications for security flaws by simulating attacks.

DRIDirectly Responsible Individual

Directly responsible individuals at GitLab own particular projects, initiatives, or activity.

EMEAEurope, Middle East, and Africa

Europe, the Middle East and Africa on Wikipedia.

FRTFirst Response Time

Support have a first response time Service Level Agreement (SLA) on all new tickets from subscribed customers.

GETGitLab Environment Toolkit

A toolkit provided by GitLab for setting up and managing GitLab environments. GET helps with deployment and configuration of GitLab instances.

GKEGoogle Kubernetes Engine

Google’s managed Kubernetes service that provides a hosted Kubernetes environment. GKE simplifies cluster management and integrates with other Google Cloud services.

GKGGitLab Knowledge Graph

See GitLab Knowledge Graph docs page.

gprodGoogle Production

A reference to production environments or services running on Google Cloud Platform.

HAHigh Availability

A system design approach that ensures a service remains operational and accessible even when individual components fail. HA systems minimize downtime and maintain service continuity.

JWTJSON Web Token

A compact format for transferring claims between any two parties. JWTs are commonly used for authentication and information exchange in web applications.

k8sKubernetes

Abbreviated as k8s (k + 8 letters + s), Kubernetes is a container orchestration platform that manages Docker containers across multiple servers.

KBKnowledge Base

A repository of solutions to commonly-encountered problems, created and maintained by Support Engineers. May also be used to refer to individual articles.

KCSKnowledge Centered Service

An industry standard for indetifying, creating, and updating articles within a knowledge base. Official documentation.

LDAPLightweight Directory Access Protocol

An industry-standard protocol for accessing and maintaining distributed directory information services. Commonly used for authentication and authorization in enterprise environments.

LLMLarge Language Model

See LLM in GitLab Duo Glossary.

LSPLanguage Server Protocol

See GitLab Language Server docs page.

MBRMonthly Business Review

See Support Monthly Business Review.

MCPModel Context Protocol

See Model Context Protocol docs page.

MFAMulti-Factor Authentication

A commonly used industry term.

MTTRMean Time To Resolution

A measurement of the average time it takes for a ticket to progress from creation to solved.

MVCMinimal Valuable Change

Minimal valuable change was previously referred to as the minimal viable change. This language was updated 2024-07-31.

NRT
  • Next Response Time
  • Next Reply Time

Support have a next response time Service Level Objective (SLO) on all subsequent replies to tickets from subscribed customers.

OKRObjectives and Key Results

GitLab uses OKRs to support achieving our strategic goals.

PATPersonal Access Token

See Personal Access Token.

PDPagerDuty

See How Support On-call works for more information about how GitLab Support uses PagerDuty.

PrATProject Access Token

See Project Access Token.

PSProfessional Services

The Professional Services team at GitLab is a part of the Customer Success department helping customers achieve value faster.

QBRQuarterly Business Review

A once-per-quarter meeting between a vendor (us) and their client (customer) to go over key topics. Common discussion points include vendor product and service delivery since the last meeting, progress on goals, problems that need to be addressed, and changes that need to be made. The QBR is often vital to convincing the customer to renew their contract or subscription.

RAGRetrieval-Augmented Generation

See RAG in GitLab Duo Glossary.

RFHTypically refers to Request For Help issues.

See The Request For Help Landing Page.

RWTRequester wait time

See Metrics definition.

SASTStatic Application Security Testing

A security testing method that scans source code for vulnerabilities without running the application.

SBOMSoftware Bill Of Materials

You can read all about SBOMs in our blog post.

SGGSupport Global Group

A reference to GitLab’s global support organization structure. SGG encompasses support teams across different regions and time zones.

SHMSelf-Hosted Models

See GitLab Duo Self-Hosted docs page.

SLAService Level Agreement

GitLab Support service level agreements might differ from other definitions in other departments.

SLOService Level Objective

Support has an internal service level objective on all subsequent responses to tickets after the first response. We use the SLA timer in Zendesk to track this.

SMESubject Matter Expert

An individual with deep knowledge and expertise in a specific area or technology. SMEs are often consulted for complex technical issues requiring specialized knowledge.

SMOCSupport Manager On-call

See How to be a Support Manager On-call.

SPSSuccess Plan Services

See this internal Handbook page, which is the SSoT for SPS.

SRESite Reliability Engineer

Site Reliability Engineers (SREs) are responsible for keeping all user-facing services and other GitLab production systems running smoothly. You can read more here

SSATSupport Satisfaction

We use SSAT to capture customer feedback and measure customer satisfaction.

SSCSupport Stable Counterpart

Support engineers who work closely with development teams to provide expertise and feedback.

SSESenior Support Engineer

A senior-level support engineer role within GitLab Support. SSEs typically handle more complex technical issues and may mentor other support engineers.

STARSupport Ticket Attention Requests

STAR is used when a support ticket needs extra visibility or prioritization. This is typically communicated in the #support_ticket-attention-requests Slack channel.

SWIRSupport Week In Review

See Support Week In Review project.

T&STrust and Safety

A team responsible for maintaining platform safety, preventing abuse, and ensuring compliance with policies and regulations. T&S teams work to protect users and maintain platform integrity.