| stage | Data Stores |
|---|---|
| group | Application Performance |
| info | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
GitLab provides some monitoring endpoints that provide health check information when probed.
To control access to those endpoints via IP whitelisting, you can add single hosts or use IP ranges:
::Tabs
:::TabTitle Linux package (Omnibus)
-
Open
/etc/gitlab/gitlab.rband add or uncomment the following:gitlab_rails['monitoring_whitelist'] = ['127.0.0.0/8', '192.168.0.1']
-
Save the file and reconfigure GitLab for the changes to take effect.
:::TabTitle Helm chart (Kubernetes)
You can set the required IPs under the gitlab.webservice.monitoring.ipWhitelist key. For example:
gitlab:
webservice:
monitoring:
# Monitoring IP whitelist
ipWhitelist:
- 0.0.0.0/0 # Default:::TabTitle Self-compiled (source)
-
Edit
config/gitlab.yml:monitoring: # by default only local IPs are allowed to access monitoring resources ip_whitelist: - 127.0.0.0/8 - 192.168.0.1
-
Save the file and restart GitLab for the changes to take effect.
::EndTabs