package v1.public.events.fusion.invocation

Get desktop application:
View/edit binary Protocol Buffers messages

Invocation event holding identifying info and flattened attributes.

• string invocation_id = 1

  UUID string for the invocation id, either as passed in via args or generated (UUIDv7 in that case). Note, that `trace_id` is the same value stored as bytes and generally preferred for correlation with other events as it is present on all telemetry records.

• string raw_command = 2

  Raw command string as executed.

• optional InvocationEvalArgs eval_args = 3

  Structured evaluation arguments.

• optional process.Process process_info = 4

  Process-wide attributes.

• optional InvocationMetrics metrics = 5

  Aggregate invocation metrics.

• optional uint64 parent_span_id = 6

  Optional parent span ID for trace correlation. This allows linking this invocation to an external trace.

Structured evaluation arguments for the invocation.

Used in: Invocation

• string command = 1

  The dbt command executed, e.g. "run", "test", "build".

• optional string profiles_dir = 2

  The profile directory to load the profiles from

• optional string packages_install_path = 3

  The directory to install packages

• optional string target = 4

  dbt target, e.g. "dev", "prod"

• optional string profile = 5

  Profile name used for the invocation

• string vars = 6

  Vars to pass to the jinja environment. JSON blob string.

• optional uint64 limit = 7

  Limiting number of shown rows. None means no limit; --limit -1 to remove limit

• optional uint64 num_threads = 8

  The number of threads to use

• optional string selector = 9

  yaml selector

• repeated string select = 10

  Select nodes to operate on

• repeated string exclude = 11

  Select nodes to exclude from selected nodes

• optional string indirect_selection = 12

  Indirect selection mode

• repeated string output_keys = 13

  Show output keys

• repeated string resource_types = 14

  Resource types to filter by

• repeated string exclude_resource_types = 15

  Exclude nodes of a specific type

• optional bool debug = 16

  Debug flag

• optional string log_format = 17

  Logging format

• optional string log_level = 18

  Minimum severity for console/log file

• optional string log_path = 19

  'log-path' for the current run, overriding 'DBT_LOG_PATH'.

• optional string target_path = 20

  The output directory for all produced assets

• optional string project_dir = 21

  The directory to load the dbt project from

• optional bool quiet = 22

  Suppress all non-error logging to stdout

• optional bool write_json = 23

  Write JSON artifacts to disk

• optional bool write_catalog = 24

  Write a catalog.json file to the target directory

• optional bool manage_state = 25

  Whether dbt State management (auto-deferral) is enabled for this invocation, resolved from --manage-state, DBT_ENGINE_MANAGE_STATE, or `flags.manage_state` in dbt_project.yml / user settings.

Aggregate invocation metrics.

Used in: Invocation

• optional uint64 total_errors = 1

• optional uint64 total_warnings = 2

• optional uint64 autofix_suggestions = 3

• map<string, uint64> node_type_counts = 4

  Counts of nodes processed by node type (e.g., "model", "test", "seed"). Key is the lowercase node type name.

• map<string, uint64> status_counts = 5

  Counts of node outcomes by status category. Keys are: "success", "warn", "error", "reused", "skipped", "canceled", "no_op". Only non-zero counts are included.