-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
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
Add flag to disable tracing activation #2191
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2191 +/- ##
==========================================
+ Coverage 61.60% 61.66% +0.05%
==========================================
Files 154 154
Lines 12310 12311 +1
==========================================
+ Hits 7583 7591 +8
+ Misses 4120 4108 -12
- Partials 607 612 +5
|
cmd/loki/loki-local-config.yaml
Outdated
@@ -43,3 +43,6 @@ chunk_store_config: | |||
table_manager: | |||
retention_deletes_enabled: false | |||
retention_period: 0s | |||
|
|||
tracing: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need to change the local config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I just don't think we need to change the current config, but this seems like a good addition, I don't really like ENV var configuration so this is better.
Thank you !
btw you need to sign the CLA. |
Interesting that you say that, the cla bot seems to not work if I commit from my secondary e-mail which is my red hat e-mail. |
What this PR does / why we need it:
This PR addresses the capability to disable tracing per configuration flag in enviroments where the Jaeger env variables are in place and thus auto-activate tracing. The config flag comes in hand as an user provided override to disable tracing if required.
Which issue(s) this PR fixes:
Fixes #2183
Checklist