package v1.public.events.metadata_telemetry

Get desktop application:
View/edit binary Protocol Buffers messages

• optional events.vortex.VortexMessageEnrichment enrichment = 1

  Server enrichment for this event

• optional common.vortex_telemetry_contexts.VortexTelemetryDbtCloudContext context = 2

  dbt Cloud Context around this request

• string handoff_from = 3

  originating feature; see HandoffFrom for possible values

• string handoff_to = 4

  target feature; see HandoffTo for possible values

• bool is_final_handoff_action = 5

  true if this completes the handoff experience

• string handoff_action = 6

  applicable only if a handoff has different types, ex. 'Catalog -> Canvas' handoff can 'create' or 'edit'

• string asset_type = 7

  asset type of resource being handed off; see HandoffAssetType for possible values

• HANDOFF_ASSET_TYPE_UNSPECIFIED = 0

• HANDOFF_ASSET_TYPE_DBT_MODEL = 1

• HANDOFF_ASSET_TYPE_DBT_SOURCE = 2

• HANDOFF_ASSET_TYPE_DBT_SNAPSHOT = 3

• HANDOFF_ASSET_TYPE_DBT_SEED = 4

• HANDOFF_ASSET_TYPE_DBT_METRIC = 5

• HANDOFF_ASSET_TYPE_DBT_SAVED_QUERY = 6

• HANDOFF_ASSET_TYPE_DATA_WAREHOUSE_TABLE = 7

• HANDOFF_ASSET_TYPE_DATA_WAREHOUSE_VIEW = 8

As of 2025/05, enums are not handled properly with Vortex so we will be documenting them but not using them in the proto

• HANDOFF_FROM_UNSPECIFIED = 0

• HANDOFF_FROM_CATALOG = 1

• HANDOFF_TO_UNSPECIFIED = 0

• HANDOFF_TO_CATALOG = 1

• HANDOFF_TO_IDE = 2

• HANDOFF_TO_CANVAS = 3

• HANDOFF_TO_INSIGHTS = 4