Tools
dbt-core 1.12.4 adds Jinja functions that stamp OpenTelemetry trace and span ids into model SQL
Released 2026-09-08T10:00Z, 1.12.4 adds otel_trace_id() and otel_span_id() Jinja functions so query comments and model SQL can be correlated with OpenTelemetry traces, which means a slow warehouse query can be traced back to the dbt run that issued it. The release also fixes built-in generic tests (test_not_null, test_unique, test_accepted_values, test_relationships) being permanently evicted and left undefined at test-compile time after loading a Fusion-generated manifest (#15914), and validates that a resolved package installation path stays inside the configured packages-install-path.
Source
↳ Follow the thread