-
Notifications
You must be signed in to change notification settings - Fork 51
fix: disable Client Side Stats by default #756
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
Changes from 3 commits
aa8289e
1f26483
680a0f0
ff44638
04ae6c7
60484cf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -141,6 +141,9 @@ def _reset(self): | |
| "enabled" if config.fips_mode_enabled else "not enabled", | ||
| ) | ||
|
|
||
| # disable css by default to prevent double counting in lambda | ||
| if "DD_TRACE_COMPUTE_STATS" not in os.environ: | ||
| os.environ["DD_TRACE_COMPUTE_STATS"] = "false" | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do both
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good. Theyre essentially used as aliases in the python tracer.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there any reason we'd want to allow users to enable client-side stats? If not, we should just set this env var always.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. following up on whether we should or should not allow customers to set it.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. very good points. I'll just invariably set the env then |
||
|
|
||
| if ( | ||
| "DD_INSTRUMENTATION_TELEMETRY_ENABLED" not in os.environ | ||
|
|
||
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.
Should we ignore this ENV even it's set ? we can generate a warning if we found it's set to true and tell the customer this should always be off?
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.
The warning is a good idea though I dont think we should block the option completely. If the user sees the warning they can choose whether or not to ignore it. I think @happynancee had the same idea