-
Notifications
You must be signed in to change notification settings - Fork 104
Description
What happened: After clicking the View logs buttom on some trace, Grafana opens a window for logs drilldown by that clicked trace id. In opened window there is a filter for that trace id already created, but "Trace ID" column is hardcoded - so it's not available to set it or map to some column in database like in datasource settings of clickhouse-datasource plugin.
What you expected to happen: The TraceID column can be mapped in datasource settings and logs drilldown correctly works
How to reproduce it (as minimally and precisely as possible):
Before this, make sure to have two Clickhouse tables - with logs and traces, where each of them has TraceId column. Also, map the columns in database to corresponding names in clickhouse datasource settings (Logs configuration/Traces configuration).
As a start you can use next resources:
- https://clickhouse.com/blog/storing-log-data-in-clickhouse-fluent-bit-vector-open-telemetry#data--schema
- https://clickhouse.com/blog/storing-traces-and-spans-open-telemetry-in-clickhouse#schema
- Go to 'Explore'
- Get some traces by selecting some database with them and select
Tracesas Query Type - Click on some traceId in the list down below, select
View logs - See the query that not corresponds the traceId filter filled above
Screenshots
The traceId selection to view logs:

Environment:
- Grafana version: v12.2.1 (563109b696)
- Plugin version: 4.11.2
- OS Grafana is installed on: docker image
- User OS & Browser: Windows/Google Chrome
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
