#support

Resolving Time Series Graph Display Issue in 0.21.0 Frontend

TLDR Rudy had an issue displaying time series graphs after upgrading. Srikanth suggested using reserved names in ClickHouse queries. This solution worked.

Powered by Struct AI
heart1
3
2mo
Solved
Join the chat
Jul 04, 2023 (2 months ago)
Rudy
Photo of md5-33e8198fb69216ff3ec750e3d409900b
Rudy
08:07 PM
guys getting a weird issue in 0.21.0 frontend after upgrade from 0.18.3 (i ran the migration scripts). Time series graphs are not displaying in dashboard

clickhouse query
SELECT quantile(0.5)(durationNano/1e6) as p50, name, toDateTime(toStartOfMinute(timestamp)) AS ts FROM signoz_traces.signoz_index_v2 WHERE serviceName='testapp' AND timestamp>=toDateTime(intDiv({{.SIGNOZ_START_TIME}}, 1000)) AND timestamp<=toDateTime(intDiv({{.SIGNOZ_END_TIME}}, 1000)) AND name like 'GET /%' GROUP BY name,ts ORDER BY p50 DESC LIMIT 1000
Image 1 for guys getting a weird issue in 0.21.0 frontend after upgrade from 0.18.3 (i ran the migration scripts). Time series graphs are not displaying in dashboard<br><br>clickhouse query<br><code>SELECT quantile(0.5)(durationNano/1e6) as p50, name, toDateTime(toStartOfMinute(timestamp)) AS ts FROM signoz_traces.signoz_index_v2 WHERE serviceName=&#x27;testapp&#x27; AND timestamp&amp;gt;=toDateTime(intDiv({{.SIGNOZ_START_TIME}}, 1000)) AND timestamp&amp;lt;=toDateTime(intDiv({{.SIGNOZ_END_TIME}}, 1000)) AND name like &#x27;GET /%&#x27; GROUP BY name,ts ORDER BY p50 DESC LIMIT 1000</code>
Jul 05, 2023 (2 months ago)
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
01:48 AM
When you write ClickHouse queries, you need to give the result column with the reserved name, any of these work value, result. Use them instead of p50, and it should work. The reason is you could have another number part of the select clause such as http_status_code so there needs to be some way to distinct between the result column vs the rest.
heart1
Rudy
Photo of md5-33e8198fb69216ff3ec750e3d409900b
Rudy
05:09 PM
thank you that worked!