The /services API omits services whose names start with '@' even though service data exists in ClickHouse. This happens because our query building embeds the service name as a string literal inside a resource-fingerprint subquery, and the clickhouse-go named-parameter binder later scans the entire SQL and mistakenly treats the leading '@' inside that quoted literal as a parameter placeholder.

We build a resource-fingerprint subquery and inline it into the main query. The subquery currently embeds the service name literal:

That subquery string is concatenated into the outer SQL and then passed to the driver binder. The clickhouse-go binder uses a regex for named parameters that is not quote-aware and matches “@…” anywhere in the SQL, including inside quoted string literals.

A sample resource subquery with an example service-name like @xyz :

(SELECT fingerprint FROM signoz_traces.distributed_traces_v3_resource 
WHERE (seen_at_ts_bucket_start >= 1759766587) 
AND (seen_at_ts_bucket_start <= 1759769287) 
AND simpleJSONExtractString(labels, 'deployment.environment') IN ['local'] 
AND simpleJSONExtractString(labels, 'service.name') = '@xyz' 
AND labels like '%service.name":"@xyz%')

And thus the query ends up producing no data.

@ at the start of the service name breaks the Services page #9251

Description

How to reproduce

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`@` at the start of the service name breaks the Services page #9251