Slackbot
01/17/2023, 10:52 AMnitya-signoz
01/17/2023, 10:54 AMenv
and level
to selected fields first, from the UI. This will reduce the load on the database.Jason Brewer
01/17/2023, 10:54 AMJason Brewer
01/17/2023, 10:56 AMnitya-signoz
01/17/2023, 10:56 AMselect toStartOfInterval(fromUnixTimestamp64Nano(timestamp), INTERVAL 1 MINUTE) AS interval, quantile(0.9)(bytes) as value from signoz_logs.logs where timestamp > toUnixTimestamp64Nano(now64() - INTERVAL 30 MINUTE) group by interval order by interval asc;
Eg:- here I have used the bytes
which is a selected field.Jason Brewer
01/17/2023, 10:58 AMselect
toStartOfInterval(fromUnixTimestamp64Nano(timestamp), INTERVAL 30 MINUTE) AS interval
, toFloat64(count()) as value
, level
FROM signoz_logs.distributed_logs
WHERE timestamp BETWEEN {{.start_timestamp_nano}} AND {{.end_timestamp_nano}} and level = 'error'
GROUP BY interval, level;
Jason Brewer
01/17/2023, 11:01 AMsignoz_logs.logs
and signoz_logs.distributed_logs
. From reading other messages on here it seems like distributed_logs
operates across a clickhouse cluster?
I'm running the entire Signoz stack on a single machine via docker-compose. Presumably, for my set up at least, there should be no difference in the results returned between signoz_logs.logs
and signoz_logs.distributed_logs
?nitya-signoz
01/17/2023, 11:02 AMdistributed_logs
, it is just a wrapper on top of logs
for distributed support.Jason Brewer
01/17/2023, 11:05 AMselect
toStartOfInterval(fromUnixTimestamp64Nano(timestamp), INTERVAL 30 MINUTE) AS interval
, toFloat64(count()) as value
FROM signoz_logs.distributed_logs
WHERE timestamp BETWEEN {{.start_timestamp_nano}} AND {{.end_timestamp_nano}}
and level = 'error'
and env = 'dev'
and service = 'graphql'
GROUP BY interval;
Thanks so much @nitya-signoz!