Get desktop application:
View/edit binary Protocol Buffers messages
Used in: ,
If node_cache_reason == NODE_CACHE_REASON_STILL_FRESH, this field indicates freshness period for this node in seconds.
If node_cache_reason == NODE_CACHE_REASON_STILL_FRESH, this field indicates time since last update in seconds.
Cache reuse classification when node_skip_reason == NODE_SKIP_REASON_CACHED.
Used in:
Reused from cache - no code or data changes detected.
Reused from cache - changes detected but still within freshness window.
Reused from cache - changes detected but update criteria not met.
Reused by cloning an existing relation.
Reused by cloning an existing relation within freshness tolerance.
Reasons why a node evaluation was cabceled.
Used in: ,
User explicitly cancelled execution (e.g. ctrl-c).
Categorization of aggregated errors for debugging and retry logic. Errors form a hierarchy: if any internal error occurred, the aggregated result is INTERNAL. Otherwise if any external error occurred it is EXTERNAL. Otherwise it is USER.
Used in: ,
Internal dbt error (bug, panic, unexpected state) – not recoverable by retrying.
External system error (database down, network issue, etc.) – potentially recoverable by retrying.
User code error (SQL syntax, compilation error, etc.) that must be fixed by the user.
unique_id is the globally unique identifier for this node.
Node name.
Database where this node will be created if applicable.
Schema where this node will be created if applicable.
Name of the relation (table, view, etc.) that will be created for this node if applicable.
How this node is materialized in the data warehouse.
If materialization == NODE_MATERIALIZATION_CUSTOM, this field contains the custom materialization name.
Type of node being evaluated. Known as `resource_type` in dbt core.
Core outcome for this evaluation.
Execution phase during which this node was evaluated.
Relative path to the file containing node definition within the dbt project.
Line number (1-indexed) where the test is defined (only applicable to test nodes)
Column number (0-indexed) of where the test is defined (only applicable to test nodes)
Checksum of the node definition
Whether or not SAO was enabled for this node during evaluation. Only set for run phase.
Categorization of aggregated errors for debugging and retry logic. Present when node_outcome == NODE_OUTCOME_ERROR.
Cancellation reason. Present when node_outcome == NODE_OUTCOME_CANCELED.
Detailed reason for skipping this node. Present when node_outcome == NODE_OUTCOME_SKIPPED.
Node type specific details (e.g. test fail counts, cache use reasons).
Detailed reason why cache was used. Present when node_skip_reason == NODE_SKIP_REASON_CACHED.
Test specific outcome details. Present for test / unit test node types when node_outcome == NODE_OUTCOME_SUCCESS.
Source freshness specific outcome details. Present for source nodes with freshness checks when node_outcome == NODE_OUTCOME_SUCCESS.
Upstream node that caused this node to be skipped. Present when node_skip_reason == NODE_SKIP_REASON_UPSTREAM.
Non-test node specific outcome details. Present for non test / unit test / source node types when node_outcome == NODE_OUTCOME_SUCCESS.
Optional legacy dbt core event code (e.g. "Q018") if this event has a strict mapping to a dbt core event.
Number of rows affected by this node evaluation, if available. Only set for successful outcomes where row count is known (e.g., models, seeds).
Total time in milliseconds this node evaluation spent idle. This includes time spent waiting on internal backpressure.
Non-test node specific outcome details for a successful evaluation. node_warning_outcome is always set (non-UNSPECIFIED) for new records; UNSPECIFIED only appears in records written before this field existed (backward compat).
Used in: ,
Used in: ,
ONLY FOR DATABRICKS
ONLY FOR SNOWFLAKE
Core outcome for any node evaluation result within any phase. Represents the aggregated result of all operations in the phase
Used in: ,
Default value. Should only be set on unfinished spans
Successfully completed all operations in the phase. Some node types also store a type specific outcome for successful completion.
Failed with an aggregated error type (individual errors reported as separate events). If set, `node_error_type` with also be set to indicate the type of error.
Operation was canceled (e.g. user-initiated cancellation). If set, `node_cancel_reason` will also be set to indicate the reason for the cancelation.
Skipped evaluation for a specific reason. If set, `node_skip_reason` will also be set to indicate the reason for the skip.
Span event tracking full processing of a node across all phases. Supersedes legacy NodeStart (Q024) and NodeFinished (Q025) events.
unique_id is the globally unique identifier for this node.
Node name.
Database where this node will be created if applicable.
Schema where this node will be created if applicable.
Name of the relation (table, view, etc.) that will be created for this node if applicable.
Name of the source for source nodes.
How this node is materialized in the data warehouse.
If materialization == NODE_MATERIALIZATION_CUSTOM, this field contains the custom materialization name.
Type of node being evaluated. Known as `resource_type` in dbt core.
Core outcome for this node processing across all phases.
Last execution phase that was reached during processing (or would have been reached if not skipped).
Relative path to the file containing node definition within the dbt project.
Line number (1-indexed) where the test is defined (only applicable to test nodes)
Column number (0-indexed) of where the test is defined (only applicable to test nodes)
Checksum of the node definition
Whether or not SAO was enabled for this node during evaluation. Only set for invocations, that include the run phase.
Categorization of aggregated errors for debugging and retry logic. Present when node_outcome == NODE_OUTCOME_ERROR.
Cancellation reason. Present when node_outcome == NODE_OUTCOME_CANCELED.
Detailed reason for skipping this node. Present when node_outcome == NODE_OUTCOME_SKIPPED.
Node type specific details (e.g. test fail counts, cache use reasons).
Detailed reason why cache was used. Present when node_skip_reason == NODE_SKIP_REASON_CACHED.
Test specific outcome details. Present for test / unit test node types when node_outcome == NODE_OUTCOME_SUCCESS.
Source freshness specific outcome details. Present for source nodes with freshness checks when node_outcome == NODE_OUTCOME_SUCCESS.
Upstream node that caused this node to be skipped. Present when node_skip_reason == NODE_SKIP_REASON_UPSTREAM.
Non-test node specific outcome details. Present for non test / unit test / source node types when node_outcome == NODE_OUTCOME_SUCCESS.
Legacy dbt core event code. Always set to Q024 for start, Q025 for end.
Total duration in milliseconds of all nested NodeEvaluated spans. This reflects the actual time spent processing the node, excluding time waiting for upstream nodes.
Some node's maybe be anaklyzed but not selected for execution. This flag indicates whether the node was in the selection set.
Number of rows affected by this node processing, if available. Only set for successful outcomes where row count is known (e.g., models, seeds).
Group identifier for model level notifications
Total time in milliseconds spent idle across all nested node evaluations. This includes time spent waiting on internal backpressure.
Reasons why a node may be skipped. Only applies to nodes selected for evaluation.
Used in: ,
Skipped because an upstream dependency prevents this node from running (for any reason).
Reused from cache
Current evaluation phase disabled for this node by configuration / flags.
Operation had no effect (e.g. ephemeral models).
Current evaluation phase skipped for this node due to previous phase outcome.
Used in: ,
unique_id of the upstream node that caused this node to be skipped.
Node type, also known as "resource type" in dbt core.
Used in: ,
Second-level outcome indicating whether a successfully-completed non-test node produced warnings. Analogous to TestOutcome for test nodes. Warnings are already emitted individually as LogMessages; this field exists only to signal the presence of warnings at the outcome level.
Used in:
Used in: ,
Age of the source in seconds (time since last load)
Freshness-specific outcome details (only for SOURCE nodes with freshness checks).
Used in:
Freshness within acceptable (success) threshold.
Freshness exceeded warning threshold but below error threshold.
Freshness exceeded error threshold.
Used in: ,
Number of failing rows for this test.
Pretty printed table diff if available.
Tell consumer whether or not the failure table exists.
Test-specific outcome details (only for TEST and UNITTEST node types).
Used in:
No failures found or below warning threshold.
Failures found between warning and error thresholds.
Failures found above error threshold.