This message was deleted.

Did you mean time range from the top left ? You can use

{{SIGNOZ_START_TIME}}

and

{{SIGNOZ_END_TIME}}

.

alright thanks

These two are special variable but you can create custom variable following this https://signoz.io/docs/userguide/manage-variables/

ah great, thanks

No, there should be datetime column for x axis, float column for y axis and optional string attribute columns for different aggregation.

I'm trying to display a tag from tagMap, I will group by that tag, sort by durationNano, and display that tag that is taking the most time on average.

How are you using it in query?

WHERE

date_exec >= {{SIGNOZ_START_TIME}}

AND date_exec <= {{SIGNOZ_END_TIME}}

Ah sorry it should be

{{.SIGNOZ_START_TIME}}

and

{{.SIGNOZ_END_TIME}}

basically the go templating format.

sorry, it is still is not working

Error: API responded with 400 - encountered multiple errors: error in query-A: code: 62, message: Syntax error: failed at position 359 ('<') (line 13, col 22): <no value> AND date_exec <= <no value>. Expected one of: ANY, ALL, BETWEEN expression, string concatenation expression, list, delimited by operator of variable arity, additive expression, list, delimited by binary operators, INTERVAL operator expression, INTERVAL, TIMESTAMP operator expression, TIMESTAMP, DATE operator expression, DATE, multiplicative expression, unary expression...

Share the full query

SELECT

toStartOfMinute(date_exec) AS time,

avg(duration)

FROM

(

SELECT

toTimeZone(timestamp, 'America/Toronto') AS date_exec,

ROUND(durationNano / 1000000, 2) AS duration,

serviceName AS serviceName,

tagMap['graphql.operation.name'] AS op_name

FROM signoz_traces.durationSort ds

WHERE

date_exec >= {{.SIGNOZ_START_TIME}}

AND date_exec <= {{.SIGNOZ_END_TIME}}

AND name = 'graphql.execute'

AND op_name != ''

AND op_name != 'IntrospectionQuery'

AND serviceName = 'stage'

)

GROUP BY

time

ORDER BY time ASC WITH FILL STEP 60

Can you confirm if the request payload has these values

SIGNOZ_START_TIME

and

SIGNOZ_END_TIME

?

Sorry but how would I confirm that? I tried setting panel time preference to both global time and custom

quick huddle?

sure

You probably need to convert the epoch to datetime type.

yes, also I had to divide by 1000 first to convert it to epoch seconds first

@Allan Li Is this solved? Are you able to group by tag and sort by duration?

Yes it is good, thank you

@Srikanth Chekuri possible using promql? Or the query-builder also support this?

Query builder requires float values and promql can’t be used on traces tables, so I don’t think this can be done now.

Okay I see