Bug description
Per the docs (signoz.io/docs/dashboards/interactivity), Breakout by, View in Logs/Traces, and Filter in tables only work on Query Builder panels, since these features rewrite the panel's group-by/filters, which isn't possible against a raw ClickHouse SQL string. This is documented and makes sense architecturally.
However, this limitation isn't surfaced anywhere in the product itself, the ClickHouse Query tab gives no indication that switching to it silently disables these features. Most users won't read the interactivity docs before picking a query mode, so this becomes a confusing trial-and-error discovery rather than an informed tradeoff.
This isn't a request to change the underlying behavior (the SQL-rewriting limitation is a reasonable constraint). It's a request to surface the existing documented limitation in the UI itself, so the docs and product experience are in sync.
Expected behavior
A visible indicator in the ClickHouse Query tab (e.g. a small banner or info tooltip) noting that Breakout by, View in Logs/Traces, and Filter in tables aren't available in this mode and require Query Builder instead.
How to reproduce
- Create a new dashboard panel and switch to the "ClickHouse Query" tab
- Write a valid query and save the panel
- Try Breakout by, View in Logs/Traces, or Filter in tables on the resulting panel, nothing happens, with no explanation shown
Version information
- Signoz version: SigNoz Cloud (version not exposed in UI, continuously deployed)
- Browser version: Chrome 152.0.7977.83 (64-bit)
- Your OS and version: Windows 11 Home Single Language, Version 25H2, OS Build 26200.9168
- Your CPU Architecture (ARM/Intel): Intel, x64-based (i5-12450H)
Additional context
Happy to open a PR for the banner/tooltip if that's the direction you'd want.
Thank you for your bug report – we love squashing them!
Bug description
Per the docs (signoz.io/docs/dashboards/interactivity), Breakout by, View in Logs/Traces, and Filter in tables only work on Query Builder panels, since these features rewrite the panel's group-by/filters, which isn't possible against a raw ClickHouse SQL string. This is documented and makes sense architecturally.
However, this limitation isn't surfaced anywhere in the product itself, the ClickHouse Query tab gives no indication that switching to it silently disables these features. Most users won't read the interactivity docs before picking a query mode, so this becomes a confusing trial-and-error discovery rather than an informed tradeoff.
This isn't a request to change the underlying behavior (the SQL-rewriting limitation is a reasonable constraint). It's a request to surface the existing documented limitation in the UI itself, so the docs and product experience are in sync.
Expected behavior
A visible indicator in the ClickHouse Query tab (e.g. a small banner or info tooltip) noting that Breakout by, View in Logs/Traces, and Filter in tables aren't available in this mode and require Query Builder instead.
How to reproduce
Version information
Additional context
Happy to open a PR for the banner/tooltip if that's the direction you'd want.
Thank you for your bug report – we love squashing them!