-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 anonymous event tracking for adapter types and RPC events #1574
Milestone
Comments
drewbanin
added a commit
that referenced
this issue
Jun 26, 2019
drewbanin
added a commit
that referenced
this issue
Jun 26, 2019
drewbanin
added a commit
that referenced
this issue
Jun 26, 2019
drewbanin
added a commit
that referenced
this issue
Jun 26, 2019
…e-and-rpc-requests (#1574) track adapter type and rpc requests
Closed by #1575 |
iknox-fa
pushed a commit
that referenced
this issue
Feb 8, 2022
automatic commit by git-black, original commits: 91124d2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature
Feature description
A better understanding of which databases dbt users are connecting to will help inform prioritization of new features. My instinct is that Redshift adoption is decreasing, but we don't currently have any way of knowing that!
Additionally, we should anonymously track requests to rpc endpoints. These can be simple - we just want to know if people are using the rpc functionality, and if so, which endpoints they're hitting.
TODO:
adapter
to theinvocation_env
schema, track this (viaadapter.type
) in the invocation start eventrpc_request
schema with atask
propertyWho will this benefit?
dbt's product manager (yours truly)
The text was updated successfully, but these errors were encountered: