# HG changeset patch # User Michael Kozono <mkozono@gitlab.com> # Date 1715296714 0 # Thu May 09 23:18:34 2024 +0000 # Node ID 84ade0e097a853ca1aac305362c4bcc4f16356b4 # Parent 1b3863c5237e3795f8f1b0768141813a3e0baa80 Remove mention of sidekiq.log See https://gitlab.com/gitlab-org/gitlab/-/merge_requests/149790 diff --git a/doc/settings/logs.md b/doc/settings/logs.md --- a/doc/settings/logs.md +++ b/doc/settings/logs.md @@ -294,12 +294,15 @@ ## Configuring log level/verbosity -You can configure the minimum log levels (verbosity) for the Container -Registry, GitLab Shell and Gitaly: +You can configure the minimum log levels (verbosity) for GitLab Rails, +Container Registry, GitLab Shell and Gitaly: 1. Edit `/etc/gitlab/gitlab.rb` and set the log levels: ```ruby + gitlab_rails['env'] = { + "GITLAB_LOG_LEVEL" => "WARN", + } registry['log_level'] = 'info' gitlab_shell['log_level'] = 'INFO' gitaly['configuration'] = { @@ -317,8 +320,9 @@ NOTE: You [cannot edit](https://gitlab.com/groups/gitlab-org/-/epics/6034) -the `log_level` for other GitLab logs, for example -`production_json.log`, `sidekiq.log`, and so on. +the `log_level` for certain GitLab logs, for example +`production_json.log`, `graphql_json.log`, and so on. +See also [Override default log level](https://docs.gitlab.com/ee/administration/logs/#override-default-log-level). ## Setting a custom log group