Get desktop application:
View/edit binary Protocol Buffers messages
Categorizes how a compare operation failed
Used in:
Default/unspecified
No state manifest configured (missing --state, --defer-state, or dbt Cloud auth)
The compare subcommand is not available (e.g. not licensed)
The model build step failed before compare could run
Any other unexpected failure
The compare command exited without an error but produced no diff rows. Reported with compare_success = false so analytics can segment empty runs from runs that produced actual diffs; user-facing UX shows a friendly empty panel.
Used in: ,
Compile was caused by a user saving a file
Compile was caused by an expliict compile command sent to the LSP
Compile was caused by a request to refresh sources for a project
Used in:
Error message
Error codes: https://github.com/dbt-labs/fs/blob/main/fs/sa/crates/dbt-common/src/error/codes.rs
Compile type enum
Used in: ,
Full compile
Speculative compile
Editor and extension information
Used in: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
session id (reported by the editor)
machine id (reported by the editor)
hashed mac address (reported by the editor)
version of the dbt extension
editor name (reported by the editor)
editor version (reported by the editor)
Type of interaction with the Get Started onboarding panel
Used in:
CTA clicks
Step state transitions
Step in the Get Started onboarding panel
Used in:
Status of a Get Started onboarding step
Used in:
Current grain shown in the lineage panel
Used in:
Project-level lineage (nodes are dbt resources)
Column-level lineage
Type of user interaction within the lineage panel
Used in:
Node interactions User single-clicked a node in the graph
User opened the file backing a node (double-click or context menu)
User refocused the graph on a specific node
User requested upstream-only view for a node
User requested downstream-only view for a node
Grain switches User switched from project lineage to column lineage
User switched back from column lineage to project lineage
Toolbar actions User applied a custom selector from the toolbar
User changed the active lens
User toggled the legend panel
User zoomed in via the toolbar
User zoomed out via the toolbar
User reset the graph view to fit
Outcome of a Model Docs panel cloud-enrichment attempt. One value is emitted per ExtensionModelDocsEnrichmentCompleted event.
Used in:
Why an OAuth session was adopted from the on-disk session file.
Used in:
Adopted during extension activation (loadAndSync).
Adopted just before a refresh because the file held a fresher session (syncFromFile).
Outcome of the OAuth session file load attempt at activation.
Used in:
No session file present at activation.
File present with our client_id slot; SecretStorage was updated from the file.
File present without our slot; SecretStorage tokens were written to the file.
File present without our slot, and no migratable secrets; nothing changed.
File present with a newer schema version; we refused to read or overwrite it.
Why an OAuth session was persisted to the on-disk session file.
Used in:
Persisted after a successful OAuth callback (handleCallback).
Persisted after a successful network refresh (refreshAccessToken).
Persisted during activation because SecretStorage had tokens but no file slot existed.
Status of a Query Results panel query at completion.
Used in:
Query ran and returned results without errors.
Query ran but returned an error.
User cancelled the query before it completed.
Query never ran because the target file is invalid (e.g., not part of an open dbt project).
Which entry point initiated a Query Results panel query.
Used in: ,
Triggered by Preview File on a model/SQL file.
Triggered by Preview CTE within a model.
Type of user interaction with the Query Results panel after results render.
Used in:
User sorted the result table by clicking a column header.
User copied a single cell value via context menu.
User copied the entire result set as CSV.
User opened the result set in a new editor tab.
First scroll within a single result set (subsequent scrolls are not reported).
Actual registration method used (known at completion/error)
Used in: ,
Registration completed using dbt_cloud.yml file
Registration completed via OAuth flow (web)
Registration completed via registration code flow (web)
How registration was triggered/determined at click time
Used in: ,
Registration will use credentials from dbt_cloud.yml file
Registration will proceed via web browser
Distinguishes passive impressions of a trial-light CTA from active denials of a gated action.
Used in:
A CTA/banner was rendered to the user (e.g. compare or catalog panel CTA).
The user invoked a gated action that was blocked (e.g. rename, column lineage).
User information
Used in: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
source used to get credentials for the user (dbt_cloud.yml, web)
dbt cloud user id, can be null if the user is not registered
dbt cloud hostname, can be null if the user is not registered
registration state as reported by the vscode extension
dbt cloud account identifier (globally unique, starts with "act_")
User state enum
Used in: ,
User is not registered
User is registered but not verified
User is registered and verified
User's registration has expired
Error occurred during verification
Error occurred during verification