When troubleshooting slow or failing database queries, knowing which query ran is the first thing you need, but finding it buried in the Attributes tab is painful. Now it's front and center in the span sidebar, syntax-highlighted, with prepared statement parameters already filled in.
Making database queries easy to find
A dedicated query widget was added to the span sidebar. If a span is a database span — carrying either the db.query.text or legacy db.statement attribute — the query appears prominently with syntax highlighting. No more hunting through tabs.
Query parameters for prepared statements
Several OpenTelemetry instrumentations for Java, .NET, and Python collect prepared statement parameters as db.query.parameter.<id_or_key> span attributes. These values are interpolated directly into the query so users can read it as it actually ran.
The interpolated parameters are interactive: filter them in or out, inspect individual values, copy to clipboard, or pin as a span table column.
Enabling query parameters with the Dash0 Operator for Kubernetes
Starting with Operator v0.141.0, the Dash0 Operator supports capturing query parameters via instrumentWorkloads.captureSqlQueryParameters: true in the Dash0Monitoring resource. This enables parameter collection for injected Java and .NET instrumentations. Python requires code-level configuration; other languages can use custom instrumentations.
Not using the Dash0 Operator, or libraries that collect database query parameters?
The Agent Skills (v1.3.0) help configure parameter collection for Java, .NET, and Python apps, plus custom instrumentations for languages lacking built-in support.
