package v1.public.events.fusion.log

Get desktop application:
View/edit binary Protocol Buffers messages

Log event that carries compiled SQL for a project node. `sql` may contain user data and may be scrubbed when sensitive telemetry collection is disabled.

• string relative_path = 1

  Path to the compiled SQL file, relative to project root (`in_dir`).

• string sql = 2

  Compiled SQL text. May be scrubbed.

• string unique_id = 3

  Globally unique dbt node identifier.

• string node_name = 4

  Display node name for compatibility output.

Log event that carries inline compiled SQL code.

• string sql = 1

Event emitted for each item in a list command output. This event replaces the dbt-core PrintEvent (Z052) for list operations.

• ListOutputFormat output_format = 1

  Format of the output

• string content = 2

  The actual content of the list item being displayed

• optional string unique_id = 3

  The unique_id of the node being listed (e.g., "model.my_project.my_model")

Output format for list command

Used in: ListItemOutput

• LIST_OUTPUT_FORMAT_UNSPECIFIED = 0

• LIST_OUTPUT_FORMAT_JSON = 1

• LIST_OUTPUT_FORMAT_SELECTOR = 2

• LIST_OUTPUT_FORMAT_NAME = 3

• LIST_OUTPUT_FORMAT_PATH = 4

Generic event for log messages that do not cary special meaning or additional metadata beyond the standard fields

• optional uint32 code = 1

  Optional fusion error/warning code

• optional string code_name = 16

  Optional fusion error/warning code variant name (e.g. "Generic").

• optional string dbt_core_event_code = 2

  Optional legacy dbt-core code (e.g. "Z048") if this event has a strict mapping to a dbt core event.

• compat.SeverityNumber original_severity_number = 3

  Original severity before user up/down-grade configuration applied.

• string original_severity_text = 4

• optional string unique_id = 5

  If this log message is emitted in the context of a specific node, this field should be set to the node's unique id.

• optional string file = 6

  Fusion source code file name where the log was created. Only available in debug builds.

• optional uint32 line = 7

  Fusion source code file line number where the log was created. Only available in debug builds.

• optional phase.ExecutionPhase phase = 8

  Execution phase (if known) during which this log was emitted.

• optional string package_name = 9

  Package name of the project dependency for which this log was emitted. Not set for the root project.

• optional string relative_path = 10

  Relative path to the project file where this log message originated.

• optional uint32 code_line = 11

  1-indexed line number in the project file where this log message originated.

• optional uint32 code_column = 12

  0-indexed column number in the project file where this log message originated.

• optional string expanded_relative_path = 13

  Optional expanded (compiled) file location for this log message.

• optional uint32 expanded_line = 14

• optional uint32 expanded_column = 15

A variation of a log message indicating execution progress. Unlike regular log messages, progress messages specify an action and a target, as well as optional description. Used by various commands (debug, deps, etc.) to report progress steps.

• optional string dbt_core_event_code = 1

  Optional legacy dbt-core code (e.g. "Z047" for DebugCmdOut) if this event has a strict mapping to a dbt core event.

• string action = 2

  The action being performed (e.g., "Debugging", "Loading").

• string target = 3

  The text describing the target of the action (e.g., "project", "dependencies").

• optional string description = 4

  Optional additional description providing more context.

• optional string unique_id = 5

  If this progress message is emitted in the context of a specific node, this field should be set to the node's unique id.

• optional string file = 6

  Fusion source code file name where the log was created. Only available in debug builds.

• optional uint32 line = 7

  Fusion source code file line number where the log was created. Only available in debug builds.

• optional phase.ExecutionPhase phase = 8

  Execution phase (if known) during which this log was emitted.

Event emitted when displaying inline data (e.g., from show command). This event replaces the dbt-core ShowNode event (Q041) for inline data display.

• ShowDataOutputFormat output_format = 1

  Format of the output

• string content = 2

  The data in the specified format (e.g., pretty-printed table)

• string node_name = 3

  Name of the node being shown (e.g., "my_model" or "inline")

• bool is_inline = 4

  Whether this is an inline/ad-hoc query (true) or a defined node (false)

• optional string unique_id = 5

  The unique_id of the node being shown (e.g., "model.my_project.my_model"). Unset for ad-hoc queries

• repeated string columns = 6

  Column names for the data

• string dbt_core_event_code = 7

  Legacy dbt core event code for backward compatibility (always "Q041")

Output format for list command

Used in: ShowDataOutput

• SHOW_DATA_OUTPUT_FORMAT_UNSPECIFIED = 0

• SHOW_DATA_OUTPUT_FORMAT_TEXT = 1

• SHOW_DATA_OUTPUT_FORMAT_CSV = 2

• SHOW_DATA_OUTPUT_FORMAT_TSV = 3

• SHOW_DATA_OUTPUT_FORMAT_JSON = 4

• SHOW_DATA_OUTPUT_FORMAT_NDJSON = 5

• SHOW_DATA_OUTPUT_FORMAT_YML = 6

Event emitted when displaying verbose/diagnostic output controlled by --show flag. This includes internal structures like manifests, schedules, stats, task graphs, etc.

• ShowResultOutputFormat output_format = 1

  Format of the output content.

• string content = 2

  The content to display in the specified format.

• string result_type = 3

  Type/category of the result being shown (e.g., "manifest", "schedule", "stats"). This is expected to be a short identifier.

• string title = 4

  Title to display above the content. This should NOT include ANSI color codes - coloring is applied by the output layers.

• optional string unique_id = 5

  The unique_id of the node for which information is being shown, if applicable. Unset for non-node-specific results like manifest or schedule.

Output format for ShowResult content.

Used in: ShowResult

• SHOW_RESULT_OUTPUT_FORMAT_UNSPECIFIED = 0

• SHOW_RESULT_OUTPUT_FORMAT_TEXT = 1

  Pretty-printed text format suitable for terminal display.

Event emitted when comparing nodes/configs for state modification details.

• optional string unique_id = 1

  If this log message is emitted in the context of a specific node, this field should be set to the node's unique id.

• string node_type_or_category = 2

  Node type or comparison category being evaluated.

• string check = 3

  Name of the specific comparison check.

• optional string self_value = 4

  Optional self/other values for the failed check.

• optional string other_value = 5

Event emitted when user explicitly logs messages via jinja's print() or log() functions. This event maps to dbt-core's JinjaLogInfo (I061-I063) events.

• bool is_print = 1

  True if this message was emitted via print(), false if via log()

• string dbt_core_event_code = 2

  Legacy dbt-core event code: - "I062" (JinjaLogInfo) for log info level - "I063" (JinjaLogDebug) for log debug level - "I061" (JinjaLogWarning) for log warning level - "Z052" (PrintEvent) for print statements

• optional string unique_id = 3

  If this log message is emitted in the context of a specific node, this field should be set to the node's unique FQN.

• optional phase.ExecutionPhase phase = 4

  Execution phase (if known) during which this log was emitted.

• optional string package_name = 5

  Package name (project or dependency) from which this log was emitted.

• optional uint32 line = 6

  Location within the SQL/Jinja file where print() or log() was called. Line number (1-indexed) of the print/log call in the SQL file.

• optional uint32 column = 7

  Column number (0-indexed) of the print/log call in the SQL file.

• optional string relative_path = 8

  Relative path to the SQL file containing the print/log call.