-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Document event tracking + opt-out #399
Comments
Hey @atharvai -- great question! This used to be documented, but I can't seem to find it over on Read The Docs. You can disable anonymous event tracking by adding these lines to your config:
send_anonymous_usage_stats: False You can find more info about this here I'll make sure to update the docs with this information. Thanks! |
@drewbanin the page comes back as blank on both chrome and safari Also can we please make this more well known as we don't exactly want to be sending back usage data when we dont even know what it's sending. Doesn't feel right, epsecially on internal instances |
@userbradley Sorry about that, the links above are from several years ago. You can see updated docs here: https://docs.getdbt.com/reference/global-configs#send-anonymous-usage-stats You can also see all the tracking code in this file: https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/tracking.py |
Thanks @joevandyk |
The documentation page doesn't mention how to turn the anonymous data usage off. Is still adding the snippet config:
send_anonymous_usage_stats: False
some_dbt_project:
... to the |
@polmonso Here's the docs: 👍 Yep, adding the following within your config:
send_anonymous_usage_stats: False Then after you run your next
|
Currently DBT sends tracking events to fishtown-analytics' snowplow instance. How can we disable this tracking?
sample log:
Sending event: {'category': 'dbt', 'action': 'run_model', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x00000000078A01D0>]....}
The text was updated successfully, but these errors were encountered: