Skip to content
Snippets Groups Projects
Commit d1debe18 authored by Sean McGivern's avatar Sean McGivern
Browse files

Merge branch 'mrchrisw-set-SIDEKIQ_LOG_ARGUMENTS' into 'master'

Set SIDEKIQ_LOG_ARGUMENTS in gitlab.rb

See merge request !8340
parents 0dcbd4c7 7422ea7a
No related branches found
No related tags found
1 merge request!8340Set SIDEKIQ_LOG_ARGUMENTS in gitlab.rb
Pipeline #
Loading
@@ -3,12 +3,15 @@
Loading
@@ -3,12 +3,15 @@
## Log arguments to Sidekiq jobs ## Log arguments to Sidekiq jobs
   
If you want to see what arguments are being passed to Sidekiq jobs you can set If you want to see what arguments are being passed to Sidekiq jobs you can set
the SIDEKIQ_LOG_ARGUMENTS environment variable. the `SIDEKIQ_LOG_ARGUMENTS` [environment variable]
(https://docs.gitlab.com/omnibus/settings/environment-variables.html) to `1` (true).
Example:
   
``` ```
SIDEKIQ_LOG_ARGUMENTS=1 bundle exec foreman start gitlab_rails['env'] = {"SIDEKIQ_LOG_ARGUMENTS" => "1"}
``` ```
   
It is not recommend to enable this setting in production because some Sidekiq Please note: It is not recommend to enable this setting in production because some
jobs (such as sending a password reset email) take secret arguments (for Sidekiq jobs (such as sending a password reset email) take secret arguments (for
example the password reset token). example the password reset token).
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment