# Alert Management
> 原文:[https://docs.gitlab.com/ee/user/project/operations/alert_management.html](https://docs.gitlab.com/ee/user/project/operations/alert_management.html)
* [Enable Alert Management](#enable-alert-management)
* [Enable a Generic Alerts endpoint](#enable-a-generic-alerts-endpoint)
* [Enable GitLab-managed Prometheus alerts](#enable-gitlab-managed-prometheus-alerts)
* [Enable external Prometheus alerts](#enable-external-prometheus-alerts)
* [Alert Management severity](#alert-management-severity)
* [Alert Management list](#alert-management-list)
* [Alert Management list sorting](#alert-management-list-sorting)
* [Searching alerts](#searching-alerts)
* [Alert Management statuses](#alert-management-statuses)
* [Alert Management details](#alert-management-details)
* [Update an Alert’s status](#update-an-alerts-status)
* [Create an Issue from an Alert](#create-an-issue-from-an-alert)
* [Update an Alert’s assignee](#update-an-alerts-assignee)
* [Alert system notes](#alert-system-notes)
* [View an Alert’s metrics data](#view-an-alerts-metrics-data)
* [Use cases for assigning alerts](#use-cases-for-assigning-alerts)
* [Slack Notifications](#slack-notifications)
# Alert Management[](#alert-management "Permalink")
在 GitLab 13.0 中[引入](https://gitlab.com/groups/gitlab-org/-/epics/2877) .
警報管理使開發人員可以輕松發現和查看其應用程序生成的警報. 通過在開發代碼的地方顯示警報信息,可以提高效率和知名度.
## Enable Alert Management[](#enable-alert-management "Permalink")
**注意:**您至少需要維護者[權限](../../permissions.html)才能啟用警報管理功能.
如下所述,有幾種方法可以將警報接受到您的 GitLab 項目中. 啟用任何這些方法將允許顯示警報列表. 配置警報后,訪問 您可以在項目的邊欄中[查看](#alert-management-list) **操作>警報** ,以[查看](#alert-management-list)警報[列表](#alert-management-list) .
### Enable a Generic Alerts endpoint[](#enable-a-generic-alerts-endpoint "Permalink")
GitLab 提供了通用警報端點,因此您可以接受來自第三方警報服務的警報. 請參閱有關[切換常規警報](../integrations/generic_alerts.html#setting-up-generic-alerts)的[說明](../integrations/generic_alerts.html#setting-up-generic-alerts)以添加此選項. 配置端點后,將啟用" [警報"列表](#alert-management-list) .
要用數據填充警報,請參閱為警報端點的請求[自定義有效負載](../integrations/generic_alerts.html#customizing-the-payload) .
### Enable GitLab-managed Prometheus alerts[](#enable-gitlab-managed-prometheus-alerts "Permalink")
您可以在 Kubernetes 集群上安裝 GitLab 管理的 Prometheus 應用程序. 有關更多信息,請參見[Kubernetes 上的 Managed Prometheus](../integrations/prometheus.html#managed-prometheus-on-kubernetes) . 安裝了由 GitLab 管理的 Prometheus 時,也會啟用[警報列表](#alert-management-list) .
要用數據填充警報,請參閱[GitLab 管理的 Prometheus 實例](../../../operations/metrics/index.html#managed-prometheus-instances) .
### Enable external Prometheus alerts[](#enable-external-prometheus-alerts "Permalink")
您可以配置外部管理的 Prometheus 實例,以將警報發送到 GitLab. 要設置此配置,請參閱[配置 Prometheus](../../../operations/metrics/index.html#external-prometheus-instances)文檔. 激活外部 Prometheus 配置也會啟用" [警報"列表](#alert-management-list) .
要用數據填充警報,請參閱[外部 Prometheus 實例](../../../operations/metrics/index.html#external-prometheus-instances) .
## Alert Management severity[](#alert-management-severity "Permalink")
警報的每個級別均包含一個形狀和顏色編碼獨特的圖標,以幫助您確定特定警報的嚴重性. 這些嚴重性圖標可幫助您立即確定應優先調查的警報:
[](img/alert_management_severity_v13_0.png)
警報包含以下圖標之一:
| Severity | Icon | 顏色(十六進制) |
| --- | --- | --- |
| Critical | | `#8b2615` |
| High | | `#c0341d` |
| Medium | | `#fca429` |
| Low | | `#fdbc60` |
| Info | | `#418cd8` |
| Unknown | | `#bababa` |
## Alert Management list[](#alert-management-list "Permalink")
**注意:**您將至少需要具有開發人員[權限](../../permissions.html)才能查看警報管理列表.
您可以在以下位置找到警報管理列表 項目側邊欄中的**操作>警報** . 每個警報包含以下指標:
[](img/alert_list_v13_1.png)
* **嚴重性** -警報的當前重要性及其應受到的關注.
* **開始時間** -警報觸發前多久. 此字段使用`X time ago`的標準 GitLab 模式,但細化的日期/時間工具提示支持此字段,具體取決于用戶的語言環境.
* **警報說明** - The description of the alert, which attempts to capture the most meaningful data.
* **事件計數** -警報觸發的次數.
* **問題** -指向為警報創建的事件問題的鏈接.
* **狀態** -警報的[當前狀態](#alert-management-statuses) .
### Alert Management list sorting[](#alert-management-list-sorting "Permalink")
在 GitLab 13.1 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/217745) .
警報管理列表顯示按開始時間排序的警報,但是您可以通過單擊警報管理列表中的標題來更改排序順序.
要查看列是否可排序,請將鼠標指向標題. 可排序的列在列名旁邊顯示一個箭頭,如以下示例所示:
[](img/alert_list_sort_v13_1.png)
### Searching alerts[](#searching-alerts "Permalink")
在 GitLab 13.1 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/213884) .
警報列表支持簡單的自由文本搜索.
[](img/alert_list_search_v13_1.png)
此搜索過濾以下字段:
* Title
* Description
* 監控工具
* Service
### Alert Management statuses[](#alert-management-statuses "Permalink")
每個警報都包含一個狀態下拉列表,以指示需要調查的警報. 標準警報狀態包括已`triggered` ,已`acknowledged`和已`resolved` :
* **觸發** :沒有人開始調查.
* **致謝** :有人正在積極調查問題.
* **解決** :不需要進一步的工作.
## Alert Management details[](#alert-management-details "Permalink")
**注意:**您至少需要具有開發人員[權限](../../permissions.html)才能查看警報管理詳細信息.
通過訪問[警報管理列表](#alert-management-list)并從列表中選擇一個警報,導航到警報管理詳細信息視圖.
[](img/alert_detail_overview_v13_1.png)
[](img/alert_detail_full_v13_1.png)
### Update an Alert’s status[](#update-an-alerts-status "Permalink")
警報管理詳細信息視圖使您可以更新警報狀態. 有關更多詳細信息,請參見[警報管理狀態](#alert-management-statuses) .
### Create an Issue from an Alert[](#create-an-issue-from-an-alert "Permalink")
在 GitLab 13.1 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/217745) .
警報管理詳細信息視圖使您可以創建問題,并使用從警報自動填充的描述來創建問題. 要創建問題,請單擊**創建問題**按鈕. 然后,您可以通過單擊**查看問題**按鈕從警報中**查看問題** .
關閉與警報相關的 GitLab 問題會將警報的狀態更改為"已解決". 有關[狀態](#alert-management-statuses)的更多詳細信息,請參閱[警報管理](#alert-management-statuses)狀態.
### Update an Alert’s assignee[](#update-an-alerts-assignee "Permalink")
在 GitLab 13.1 中[引入](https://gitlab.com/groups/gitlab-org/-/epics/3066) .
警報管理詳細信息視圖允許用戶更新警報受讓人.
在大型團隊中,共享警報的所有權,可能很難跟蹤誰在調查和處理警報. 警報管理詳細信息視圖使您可以更新警報受讓人:
**注意:** manbetx 客戶端打不開目前僅支持每個警報一個受讓人.
1. 要顯示當前警報列表,請單擊 **操作>警報** :
[](img/alert_list_assignees_v13_1.png)
2. 選擇所需的警報以顯示其**警報管理詳細信息視圖** :
[](img/alert_details_assignees_v13_1.png)
3. 如果右側欄沒有展開,請單擊 **展開側邊欄**以展開它.
4. 在右側欄中,找到**受讓人** ,然后點擊**編輯** . 從下拉菜單中,選擇要分配給警報的每個用戶. GitLab 為每個用戶創建一個[待辦事項列表項](../../todos.html) .
[](img/alert_todo_assignees_v13_1.png)
要刪除受讓人,請單擊" **受讓人"**下拉菜單旁邊的" **編輯"** ,然后從**受讓人**列表中取消選擇該用戶,或單擊" **未分配"** .
### Alert system notes[](#alert-system-notes "Permalink")
在 GitLab 13.1 中[引入](https://gitlab.com/groups/gitlab-org/-/epics/3066) .
當您對警報采取措施時,它會記錄為系統注釋,在"警報詳細信息"視圖中可見. 這為您提供了警報調查和分配歷史的線性時間表.
以下操作將產生系統注釋:
* [Updating the status of an alert](#update-an-alerts-status)
* [Creating an issue based on an alert](#create-an-issue-from-an-alert)
* [Assignment of an alert to a user](#update-an-alerts-assignee)
[](img/alert_detail_system_notes_v13_1.png)
### View an Alert’s metrics data[](#view-an-alerts-metrics-data "Permalink")
在 GitLab 13.2 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/217768) .
要查看警報的指標,請執行以下操作:
1. 以具有 Developer 或更高[權限](../../permissions.html)的用戶身份登錄.
2. 導航 **操作>警報** .
3. 單擊您要查看的警報.
4. 在警報標題下,單擊" **指標"**選項卡.
[](img/alert_detail_metrics_v13_2.png)
For GitLab-managed Prometheus instances, metrics data is automatically available for the alert, making it easy to see surrounding behavior. See [Managed Prometheus instances](../../../operations/metrics/index.html#managed-prometheus-instances) for information on setting up alerts.
對于外部管理的 Prometheus 實例,您可以配置警報規則以在警報中顯示圖表. 有關如何正確配置警報規則的信息,請參閱[基于警報在事件問題中嵌入指標](../../../operations/metrics/embed.html#embedding-metrics-based-on-alerts-in-incident-issues) . 有關為自己管理的 Prometheus 實例設置警報的信息,請參閱[外部](../../../operations/metrics/index.html#external-prometheus-instances) Prometheus 實例.
## Use cases for assigning alerts[](#use-cases-for-assigning-alerts "Permalink")
考慮一個由監視的不同部分組成的團隊,在單個應用程序上進行協作. 警報浮出水面之后,將警報發送給可以處理和解決警報的團隊成員非常重要.
將警報分配給多個受讓人可以簡化協作和委派. 所有分配者都顯示在團隊的工作流程中,并且所有分配者都會收到通知,從而簡化了警報的通信和所有權.
完成調查或修復警報的部分后,用戶可以在角色完成后從警報中取消分配帳戶. 可以更新[警報狀態](#alert-management-statuses)以反映警報是否已解決.
### Slack Notifications[](#slack-notifications "Permalink")
在 GitLab 13.1 中[引入](https://gitlab.com/gitlab-org/gitlab/-/issues/216326) .
當收到新的警報時,可以通過 Slack 消息向您發出警報.
有關如何進行設置的信息,請參閱[Slack Notifications Service 文檔](../integrations/slack.html) .
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license