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
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt-snowflake functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Usually organizations need some way of tracking usage / queries to Databricks/Snowflake databases. One way of doing that is setting teams/modules name in database connection / session object (via user_agent_entry).
When we create a connection using dbt, dbt sets its own details while creating a connection to real database.
For snowflake see code where we are hard-coding 'dbt' to application parameter when using snowflake python connector. Due to this we cannot override/append our details.
Following databricks like approach in dbt-snowflake will also help us.
Describe alternatives you've considered
Suggestion is mentioned above. Provide a way to append additional info to 'application' variable by using any environment variable.
Who will this benefit?
Users who use dbt to connect to Snowflake and need some way of metering/tracking the queries/usage of Snowflake by setting an application/user_agent string.
github-actionsbot
changed the title
[dbt-Snowflake] <Passing user's Application name to Snowflake session>
[ADAP-922] [dbt-Snowflake] <Passing user's Application name to Snowflake session>
Sep 28, 2023
dbeatty10
changed the title
[ADAP-922] [dbt-Snowflake] <Passing user's Application name to Snowflake session>
[ADAP-922] [Feature] Passing user's Application name to Snowflake session
Sep 28, 2023
What do you think @dataders ? The solution for dbt-databricks is in databricks/dbt-databricks#155. If we did something similar within dbt-snowflake, the relevant environment variable would be DBT_SNOWFLAKE_INVOCATION_ENV. Generalizing this approach to other adapters could either be an environment variable like DBT_{adapter}_INVOCATION_ENV or maybe a fully generalized name like DBT_USER_AGENT_ENTRY.
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.
Is this your first time submitting a feature request?
Describe the feature
Usually organizations need some way of tracking usage / queries to Databricks/Snowflake databases. One way of doing that is setting teams/modules name in database connection / session object (via user_agent_entry).
When we create a connection using dbt, dbt sets its own details while creating a connection to real database.
For snowflake see code where we are hard-coding 'dbt' to application parameter when using snowflake python connector. Due to this we cannot override/append our details.
dbt-databricks has a good approach. It allows setting 'DBT_DATABRICKS_INVOCATION_ENV' which is later on appended to 'user_agent_entry' string..
Following databricks like approach in dbt-snowflake will also help us.
Describe alternatives you've considered
Suggestion is mentioned above. Provide a way to append additional info to 'application' variable by using any environment variable.
Who will this benefit?
Users who use dbt to connect to Snowflake and need some way of metering/tracking the queries/usage of Snowflake by setting an application/user_agent string.
Are you interested in contributing this feature?
No response
Anything else?
I asked similar query here as well - https://discourse.getdbt.com/t/application-name-or-useragent-info-to-snowflake/10031
The text was updated successfully, but these errors were encountered: