We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@Linuus doing this in the clockwork process only should work as a workaround if you need it urgently. Sidekiq.configure_client do |config| config.client_middleware do |chain| chain.remove Sentry::Sidekiq::SentryContextClientMiddleware end end This will remove the trace header injection but only in the clockwork process. Make sure you don't put it in a general configuration. For the longer term, I think I will add a configuration parameter to the sidekiq gem which lets you control the trace header injection behaviour.
@Linuus doing this in the clockwork process only should work as a workaround if you need it urgently.
Sidekiq.configure_client do |config| config.client_middleware do |chain| chain.remove Sentry::Sidekiq::SentryContextClientMiddleware end end
This will remove the trace header injection but only in the clockwork process. Make sure you don't put it in a general configuration.
For the longer term, I think I will add a configuration parameter to the sidekiq gem which lets you control the trace header injection behaviour.
Originally posted by @sl0thentr0py in #2391
The text was updated successfully, but these errors were encountered:
sl0thentr0py
No branches or pull requests
Originally posted by @sl0thentr0py in #2391
The text was updated successfully, but these errors were encountered: