Fix traces.enabled as master switch for trace instrumentation#61
Merged
jstojiljkovic merged 2 commits intoJul 7, 2026
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Collaborator
|
Thanks for the contribution, merged will be released soon. 🙇 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, everyone! When I hit the problem described in this PR , I noticed, that when
traces.enabled=falsethe subsystems of tracing, liketraces.cache,traces.messengerand others, are not actually disabled and to disable them completely in test env, I had to have a config like this:I propose changing this behaviour, so that
traces.enabledwork as a master switch for all suboptions. With this we'll be able to use config like this to disable tracing in test env: