diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-31 21:07:22 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-31 21:07:22 +0300 |
| commit | 1d21e1712158ee4e3cf8b71b45ead662529fc3f8 (patch) | |
| tree | a8435cf28a026d7d7ef681d459e905bcf5609f65 /doc/administration | |
| parent | 47bf4294773cf15aa755193cdd7df9a491a49f52 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration')
4 files changed, 16 insertions, 2 deletions
diff --git a/doc/administration/auditor_users.md b/doc/administration/auditor_users.md index e9df9cc6e37..09d68e82782 100644 --- a/doc/administration/auditor_users.md +++ b/doc/administration/auditor_users.md @@ -25,6 +25,9 @@ Situations where auditor access for users could be helpful include: you can create an account with auditor access and then share the credentials with those users to which you want to grant access. +NOTE: +An auditor user counts as a billable user and consumes a license seat. + ## Add a user with auditor access To create a new user account with auditor access (or change an existing user): diff --git a/doc/administration/monitoring/prometheus/web_exporter.md b/doc/administration/monitoring/prometheus/web_exporter.md index a2dee80f6d4..fbf4a109813 100644 --- a/doc/administration/monitoring/prometheus/web_exporter.md +++ b/doc/administration/monitoring/prometheus/web_exporter.md @@ -71,3 +71,11 @@ To serve metrics via HTTPS instead of HTTP, enable TLS in the exporter settings: When TLS is enabled, the same `port` and `address` is used as described above. The metrics server cannot serve both HTTP and HTTPS at the same time. + +## Troubleshooting + +### Docker container runs out of space + +When running [GitLab in Docker](../../../install/docker.md), your container might run out of space. This can happen if you enable certain features which increase your space consumption, for example Web Exporter. + +To work around this issue, [update your `shm-size`](../../../install/docker.md#devshm-mount-not-having-enough-space-in-docker-container). diff --git a/doc/administration/settings/rate_limits_on_git_ssh_operations.md b/doc/administration/settings/rate_limits_on_git_ssh_operations.md index 677d8fea195..4e60fd55b19 100644 --- a/doc/administration/settings/rate_limits_on_git_ssh_operations.md +++ b/doc/administration/settings/rate_limits_on_git_ssh_operations.md @@ -20,8 +20,6 @@ Each command has a rate limit of 600 per minute. For example: Because the same commands are shared by `git-upload-pack`, `git pull`, and `git clone`, they share a rate limit. -Users on self-managed GitLab can disable this rate limit. - ## Configure GitLab Shell operation limit > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/123761) in GitLab 16.2. @@ -33,4 +31,5 @@ Users on self-managed GitLab can disable this rate limit. 1. Select **Settings > Network**. 1. Expand **Git SSH operations rate limit**. 1. Enter a value for **Maximum number of Git operations per minute**. + - To disable the rate limit, set it to `0`. 1. Select **Save changes**. diff --git a/doc/administration/settings/scim_setup.md b/doc/administration/settings/scim_setup.md index 432c8598cf7..45020fdfb59 100644 --- a/doc/administration/settings/scim_setup.md +++ b/doc/administration/settings/scim_setup.md @@ -53,3 +53,7 @@ adding them to the SCIM identity provider. After the identity provider performs a sync based on its configured schedule, the user's SCIM identity is reactivated and their GitLab instance access is restored. + +## Troubleshooting + +See our [troubleshooting SCIM guide](../../user/group/saml_sso/troubleshooting_scim.md). |