# Monitoring GitLab with Prometheus
> 原文:[https://docs.gitlab.com/ee/administration/monitoring/prometheus/](https://docs.gitlab.com/ee/administration/monitoring/prometheus/)
* [Overview](#overview)
* [Configuring Prometheus](#configuring-prometheus)
* [Changing the port and address Prometheus listens on](#changing-the-port-and-address-prometheus-listens-on)
* [Adding custom scrape configurations](#adding-custom-scrape-configurations)
* [Using an external Prometheus server](#using-an-external-prometheus-server)
* [Viewing performance metrics](#viewing-performance-metrics)
* [Prometheus as a Grafana data source](#prometheus-as-a-grafana-data-source)
* [GitLab metrics](#gitlab-metrics)
* [Bundled software metrics](#bundled-software-metrics)
* [Node exporter](#node-exporter)
* [Redis exporter](#redis-exporter)
* [PostgreSQL exporter](#postgresql-exporter)
* [PgBouncer exporter](#pgbouncer-exporter)
* [Registry exporter](#registry-exporter)
* [GitLab exporter](#gitlab-exporter)
* [Configuring Prometheus to monitor Kubernetes](#configuring-prometheus-to-monitor-kubernetes)
# Monitoring GitLab with Prometheus[](#monitoring-gitlab-with-prometheus "Permalink")
> **Notes:**
>
> * 本頁中列出的 Prometheus 和各種出口商都捆綁在 Omnibus GitLab 軟件包中. 查看每個出口商的文檔以了解添加的時間表. 對于源安裝,您必須自己安裝. 在后續版本中,將捕獲其他的 GitLab 指標.
> * GitLab 9.0 默認情況下會啟用 Prometheus 服務.
> * Prometheus 及其出口商不對用戶進行身份驗證,任何可以訪問它們的人都可以使用.
[Prometheus](https://s0prometheus0io.icopy.site)是一項功能強大的時間序列監視服務,為監視 GitLab 和其他軟件產品提供了靈活的平臺. GitLab 提供了 Prometheus 的開箱即用監視功能,可輕松訪問 GitLab 服務的高質量時間序列監視.
## Overview[](#overview "Permalink")
Prometheus 的工作方式是定期連接到數據源,并通過[各種出口商](#bundled-software-metrics)收集其績效指標. 要查看和使用監視數據,您可以[直接連接到 Prometheus](#viewing-performance-metrics)或使用儀表板工具(例如[Grafana)](https://grafana.com) .
## Configuring Prometheus[](#configuring-prometheus "Permalink")
**注意:**對于源安裝,您必須自己安裝和配置.
從 GitLab 9.0 開始,Prometheus 及其出口商默認情況下處于打開狀態. Prometheus 將以`gitlab-prometheus`用戶身份運行,并監聽`http://localhost:9090` . 默認情況下,只能從 GitLab 服務器本身訪問 Prometheus. 除非單獨禁用,否則每個出口商將自動設置為 Prometheus 的監視目標.
要禁用 Prometheus 及其所有出口商以及將來添加的任何出口商,請執行以下操作:
1. Edit `/etc/gitlab/gitlab.rb`
2. 添加或查找并取消注釋以下行,確保將其設置為`false` :
```
prometheus_monitoring['enable'] = false
```
3. 保存文件并[重新配置 GitLab,](../../restart_gitlab.html#omnibus-gitlab-reconfigure)以使更改生效.
### Changing the port and address Prometheus listens on[](#changing-the-port-and-address-prometheus-listens-on "Permalink")
**注意:** [Omnibus GitLab 8.17 中](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1261)添加了以下更改. 盡管可能,但不建議更改 Prometheus 監聽的端口,因為這可能會影響 GitLab 服務器上運行的其他服務或與之沖突. 繼續需要您自擔風險.
為了從 GitLab 服務器外部訪問 Prometheus,您需要在`prometheus['listen_address']`設置 FQDN 或 IP. 更改 Prometheus 監聽的地址/端口:
1. Edit `/etc/gitlab/gitlab.rb`
2. 添加或查找并取消注釋以下行:
```
prometheus['listen_address'] = 'localhost:9090'
```
將`localhost:9090`替換為您希望 Prometheus 監聽的地址或端口. 如果要允許除`localhost`以外的其他主機訪問 Prometheus,請忽略該主機,或使用`0.0.0.0`允許公共訪問:
```
prometheus['listen_address'] = ':9090'
# or
prometheus['listen_address'] = '0.0.0.0:9090'
```
3. 保存文件并[重新配置 GitLab,](../../restart_gitlab.html#omnibus-gitlab-reconfigure)以使更改生效
### Adding custom scrape configurations[](#adding-custom-scrape-configurations "Permalink")
您可以使用[Prometheus 刮擦目標配置](https://s0prometheus0io.icopy.site/docs/prometheus/latest/configuration/configuration/)語法在`/etc/gitlab/gitlab.rb`編輯`prometheus['scrape_configs']` , `/etc/gitlab/gitlab.rb`為 Omnibus GitLab 捆綁的 Prometheus 配置其他刮擦目標.
這是刮取`http://1.1.1.1:8060/probe?param_a=test¶m_b=additional_test`的示例配置:
```
prometheus['scrape_configs'] = [
{
'job_name': 'custom-scrape',
'metrics_path': '/probe',
'params' => {
'param_a' => ['test'],
'param_b' => ['additional_test']
},
'static_configs' => [
'targets' => ['1.1.1.1:8060'],
],
},
]
```
### Using an external Prometheus server[](#using-an-external-prometheus-server "Permalink")
**注意:** Prometheus 和大多數導出器不支持身份驗證. 我們不建議將它們公開在本地網絡之外.
需要進行一些配置更改,才能由外部 Prometheus 服務器監視 GitLab. 對于[具有多個節點的 GitLab 部署,](../../reference_architectures/index.html)建議使用外部服務器.
要使用外部 Prometheus 服務器:
1. Edit `/etc/gitlab/gitlab.rb`.
2. 禁用捆綁的 Prometheus:
```
prometheus['enable'] = false
```
3. 將每個捆綁服務的[導出器設置](#bundled-software-metrics)為偵聽網絡地址,例如:
```
gitlab_exporter['listen_address'] = '0.0.0.0'
sidekiq['listen_address'] = '0.0.0.0'
gitlab_exporter['listen_port'] = '9168'
node_exporter['listen_address'] = '0.0.0.0:9100'
redis_exporter['listen_address'] = '0.0.0.0:9121'
postgres_exporter['listen_address'] = '0.0.0.0:9187'
gitaly['prometheus_listen_addr'] = "0.0.0.0:9236"
gitlab_workhorse['prometheus_listen_addr'] = "0.0.0.0:9229"
```
4. 如有必要,請使用[官方安裝說明](https://s0prometheus0io.icopy.site/docs/prometheus/latest/installation/)安裝并設置專用的 Prometheus 實例.
5. 將 Prometheus 服務器 IP 地址添加到[監視 IP 白名單](../ip_whitelist.html) . 例如:
```
gitlab_rails['monitoring_whitelist'] = ['127.0.0.0/8', '192.168.0.1']
```
6. 在**所有** GitLab Rails(Puma / Unicorn,Sidekiq)服務器上,設置 Prometheus 服務器 IP 地址和監聽端口. 例如:
```
gitlab_rails['prometheus_address'] = '192.168.0.1:9090'
```
7. 要抓取 NGINX 指標,您還需要配置 NGINX 以允許 Prometheus 服務器 IP. 例如:
```
nginx['status']['options'] = {
"server_tokens" => "off",
"access_log" => "off",
"allow" => "192.168.0.1",
"deny" => "all",
}
```
8. [重新配置 GitLab](../../restart_gitlab.html#omnibus-gitlab-reconfigure)以應用更改.
9. 編輯 Prometheus 服務器的配置文件.
10. 將每個節點的導出器添加到 Prometheus 服務器的[抓取目標配置中](https://s0prometheus0io.icopy.site/docs/prometheus/latest/configuration/configuration/) . 例如,使用`static_configs`的樣本片段:
```
scrape_configs:
- job_name: nginx
static_configs:
- targets:
- 1.1.1.1:8060
- job_name: redis
static_configs:
- targets:
- 1.1.1.1:9121
- job_name: postgres
static_configs:
- targets:
- 1.1.1.1:9187
- job_name: node
static_configs:
- targets:
- 1.1.1.1:9100
- job_name: gitlab-workhorse
static_configs:
- targets:
- 1.1.1.1:9229
- job_name: gitlab-rails
metrics_path: "/-/metrics"
static_configs:
- targets:
- 1.1.1.1:8080
- job_name: gitlab-sidekiq
static_configs:
- targets:
- 1.1.1.1:8082
- job_name: gitlab_exporter_database
metrics_path: "/database"
static_configs:
- targets:
- 1.1.1.1:9168
- job_name: gitlab_exporter_sidekiq
metrics_path: "/sidekiq"
static_configs:
- targets:
- 1.1.1.1:9168
- job_name: gitlab_exporter_process
metrics_path: "/process"
static_configs:
- targets:
- 1.1.1.1:9168
- job_name: gitaly
static_configs:
- targets:
- 1.1.1.1:9236
```
11. 重新加載 Prometheus 服務器.
## Viewing performance metrics[](#viewing-performance-metrics "Permalink")
您可以訪問`http://localhost:9090` ,以獲取 Prometheus 默認提供的儀表板.
> **注意:**如果在您的 GitLab 實例上啟用了 SSL,由于[HSTS,](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)如果使用相同的 FQDN,則可能無法在與 GitLab 相同的瀏覽器上訪問 Prometheus. 我們計劃[通過 GitLab 提供訪問](https://gitlab.com/gitlab-org/multi-user-prometheus) ,但是在此期間,有一些解決方法:使用單獨的 FQDN,使用服務器 IP,使用單獨的 Prometheus 瀏覽器,重置 HSTS 或使用[NGINX 代理](https://docs.gitlab.com/omnibus/settings/nginx.html) .
Prometheus 收集的性能數據可以在 Prometheus 控制臺中直接查看,也可以通過兼容的儀表板工具查看. Prometheus 界面提供了一種[靈活的查詢語言](https://s0prometheus0io.icopy.site/docs/prometheus/latest/querying/basics/) ,可與收集的數據一起使用,您可以在其中可視化輸出. 要獲得功能更全面的儀表板,可以使用 Grafana 并已[對 Prometheus 進行了官方支持](https://s0prometheus0io.icopy.site/docs/visualization/grafana/) .
普羅米修斯樣本查詢:
* **可用內存百分比:** `((node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes) or ((node_memory_MemFree_bytes + node_memory_Buffers_bytes + node_memory_Cached_bytes) / node_memory_MemTotal_bytes)) * 100`
* **CPU 使用率百分比:** `1 - avg without (mode,cpu) (rate(node_cpu_seconds_total{mode="idle"}[5m]))`
* **傳輸的數據:** `rate(node_network_transmit_bytes_total{device!="lo"}[5m])`
* **收到的數據:** `rate(node_network_receive_bytes_total{device!="lo"}[5m])`
## Prometheus as a Grafana data source[](#prometheus-as-a-grafana-data-source "Permalink")
Grafana 允許您導入 Prometheus 性能指標作為數據源,并將指標呈現為圖形和儀表板,這有助于可視化.
To add a Prometheus dashboard for a single server GitLab setup:
1. 在 Grafana 中創建一個新的數據源.
2. 命名您的數據源(如 GitLab).
3. 在類型下拉框中選擇`Prometheus` .
4. 將您的 Prometheus 偵聽地址添加為 URL,并設置對`Browser`訪問權限.
5. 將 HTTP 方法設置為`GET` .
6. 保存并測試您的配置以驗證其是否有效.
## GitLab metrics[](#gitlab-metrics "Permalink")
在 GitLab 9.3 中引入.
GitLab 監視其自身的內部服務指標,并使其在`/-/metrics`端點可用. 與其他導出器不同,此終結點需要身份驗證,因為它可以在與用戶流量相同的 URL 和端口上使用.
[? Read more about the GitLab Metrics.](gitlab_metrics.html)
## Bundled software metrics[](#bundled-software-metrics "Permalink")
Omnibus GitLab 中捆綁的許多 GitLab 依賴項都已預先配置為導出 Prometheus 指標.
### Node exporter[](#node-exporter "Permalink")
節點導出器允許您測量各種機器資源,例如內存,磁盤和 CPU 利用率.
[Read more about the node exporter](node_exporter.html).
### Redis exporter[](#redis-exporter "Permalink")
Redis 導出器允許您測量各種 Redis 指標.
[Read more about the Redis exporter](redis_exporter.html).
### PostgreSQL exporter[](#postgresql-exporter "Permalink")
PostgreSQL 導出器允許您測量各種 PostgreSQL 指標.
[Read more about the PostgreSQL exporter](postgres_exporter.html).
### PgBouncer exporter[](#pgbouncer-exporter "Permalink")
PgBouncer 導出器允許您測量各種 PgBouncer 指標.
[Read more about the PgBouncer exporter](pgbouncer_exporter.html).
### Registry exporter[](#registry-exporter "Permalink")
注冊表導出器允許您測量各種注冊表指標.
[Read more about the Registry exporter](registry_exporter.html).
### GitLab exporter[](#gitlab-exporter "Permalink")
GitLab 導出器允許您測量從 Redis 和數據庫中提取的各種 GitLab 指標.
[Read more about the GitLab exporter](gitlab_exporter.html).
## Configuring Prometheus to monitor Kubernetes[](#configuring-prometheus-to-monitor-kubernetes "Permalink")
版本歷史
* 在 GitLab 9.0 中引入.
* 在 GitLab 9.4 中引入了 Pod 監控.
如果您的 GitLab 服務器在 Kubernetes 中運行,則 Prometheus 將從群集中的節點和帶[注釋的](https://s0prometheus0io.icopy.site/docs/prometheus/latest/configuration/configuration/) Pod 收集指標,包括每個容器上的性能數據. 如果您的 CI / CD 環境在同一群集中運行,這將特別有用,因為您可以使用[Prometheus 項目集成](../../../user/project/integrations/prometheus.html)來監視它們.
要禁用對 Kubernetes 的監視:
1. Edit `/etc/gitlab/gitlab.rb`.
2. 添加(或查找并取消注釋)以下行并將其設置為`false` :
```
prometheus['monitor_kubernetes'] = false
```
3. 保存文件并[重新配置 GitLab,](../../restart_gitlab.html#omnibus-gitlab-reconfigure)以使更改生效.
- 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