Arch Linux

iavr

Member

Registered: 2024-02-07

Posts: 11

Log spam from GitLab Sidekiq

I've installed gitlab 16.11.1-1

It works more-or-less as it should.  One issue, however, is that it uses a default log level of "INFO", and this causes it (specifically the gitlab-sidekiq service) to generate a huge volume of not-especially-important logs.  The question is, how can I bump the log level up to "WARN" to reduce the logging overhead?

I have a solution that works, but I'm not happy with this solution because it's hackish and it gets overwritten every time gitlab updates:
- Edit the file /usr/share/webapps/gitlab/config/initializers/sidekiq.rb
- Add the following line to the Sidekiq.configure_server section:

  config.logger.level = Logger::WARN

The GitLab docs says that setting the GITLAB_LOG_LEVEL environment variable would have the effect of changing the minimum log level.  I tried to do this by creating the following /etc/systemd/system/gitlab-sidekiq.service.d/sidekiq_env.conf file:

[Service]
# ensure that logging is WARN or above only, to prevent log spam
Environment="GITLAB_LOG_LEVEL=warn"

Playing with the code, I've confirmed that: the GITLAB_LOG_LEVEL environment variable does have the correct value in sidekiq.rb, but the logger is still set to the INFO level, and the program still generates log spam.  Any ideas what I might be doing wrong?