You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
add adapter to the invocation_env schema, track this (via adapter.type) in the invocation start event
add an rpc_request schema with a task property
Who will this benefit?
dbt's product manager (yours truly)
The text was updated successfully, but these errors were encountered:
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: