Hi guys, I was wondering if this is a signoz issue...
# support
d
Hi guys, I was wondering if this is a signoz issue or a clickhouse related issue. When I run clickhouse queries in the signoz dashboard editor, it always times out after 1 minute (and thus fails, queries faster than 1 minute do not fail). So is this something that signoz does not support? Or is this a clickhouse setting that I need to change? Any help would be greatly appreciated.
a
I think this is a clickhouse setting we enabled. Do you really need your queries to be running for more than 1 min? cc @Vishal Sharma
d
Yes, we have a lot of data we are querying over. Is this a setting I could configure?
a
Is this a setting I could configure?
I will let @Vishal Sharma reply on this.
we have a lot of data we are querying over.
Is this a standard APM query or some other use case? Can you share a sample query (in simple English or SQL)? We might have ways to make it performant.
d
SELECT    quantile(0.99)(durationNano) as p99,
name,
toDateTime(toStartOfMinute(timestamp)) AS ts
FROM
()
WHERE( timestamp >= start_t
AND timestamp <= end_t
GROUP BY name,ts
ORDER BY p99 DESC
this is the basic query, it contains some more filtering to make it specific for a cluster and remove some unwanted data
v
@Daniël Boelman We have set default query timeout to 60s: https://github.com/SigNoz/signoz/blob/0bc44c6fd986ecde0513a153dd37a5baf4a7b339/pkg/query-service/constants/constants.go#L100 Currently it’s not configurable. Created an issue to allow it to be configurable via env variable, Track here: https://github.com/SigNoz/signoz/issues/2582
d
Thanks for the help! I'll keep an eye on the progress.
a
this is the basic query, it contains some more filtering to make it specific for a cluster and remove some unwanted data
do you have serviceName in the filters? The query will be faster with ServiceName.
d
yeah i do