Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

sidekiq_debugging.md

Blame
  • Forked from GitLab.org / GitLab FOSS
    1976 commits behind the upstream repository.
    sidekiq_debugging.md 544 B

    Sidekiq debugging

    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] (https://docs.gitlab.com/omnibus/settings/environment-variables.html) to 1 (true).

    Example:

    gitlab_rails['env'] = {"SIDEKIQ_LOG_ARGUMENTS" => "1"}

    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).