feat: add initial connection telemetry log - #1620
Draft
saishreeeee wants to merge 2 commits into
Draft
Conversation
saishreeeee
marked this pull request as draft
July 29, 2026 10:16
saishreeeee
marked this pull request as ready for review
July 29, 2026 10:55
sd-db
marked this pull request as draft
July 29, 2026 12:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Opt-in, initial connection telemetry log sent once to /telemetry-ext on first connection; enable via enable_dbt_telemetry in connection_parameters (default off).
Testing:
Manually tested against a live SPOG workspace with enable_dbt_telemetry: true,
dbt debug emitted one connection log to /telemetry-ext and the server accepted it (200, numProtoSuccess: 1, no errors);
confirmed the row lands in the driver telemetry table filtered on driver_name = 'dbt-databricks'.