Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
7422ea7a
Commit
7422ea7a
authored
Dec 28, 2016
by
Chris Wilson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Set SIDEKIQ_LOG_ARGUMENTS in gitlab.rb
parent
b93c72e3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
5 deletions
+8
-5
doc/development/sidekiq_debugging.md
doc/development/sidekiq_debugging.md
+8
-5
No files found.
doc/development/sidekiq_debugging.md
View file @
7422ea7a
...
...
@@ -3,12 +3,15 @@
## Log arguments to Sidekiq jobs
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
jobs (such as sending a password reset email) take secret arguments (for
example the password reset token).
Please note: It is not recommend to enable this setting in production because some
Sidekiq
jobs (such as sending a password reset email) take secret arguments (for
example the password reset token).
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment