You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Hi guys!
When creating an Alert Rule on Clickhouse datasource, you get series named after query only.
Column names given in the query itself is missing completely.
Screenshots:
Why is it important
It's common for us to select for multiple metrics in one query.
Having this problem, alert rule fires with just "Value" in payload, instead of the name of the metric.
Thus, engineers have to browse to dashboard panel and do a research on which metric has gone wrong.
What you expected to happen:
Series' labels to contain names given in SELECT clause.
How to reproduce it (as minimally and precisely as possible):
Just make a query as on the first screenshot.
Anything else we need to know?:
On a dashboard panel, this thing seems to work fine, it's an alert rule that's affected.
Environment:
Grafana version: Any 11.2+ (at least)
Plugin version: 4.3.2
OS Grafana is installed on: Dont know
User OS & Browser: Any
The text was updated successfully, but these errors were encountered:
What happened:
Hi guys!
When creating an Alert Rule on Clickhouse datasource, you get series named after query only.
Column names given in the query itself is missing completely.
Screenshots:
Why is it important
It's common for us to select for multiple metrics in one query.
Having this problem, alert rule fires with just "Value" in payload, instead of the name of the metric.
Thus, engineers have to browse to dashboard panel and do a research on which metric has gone wrong.
What you expected to happen:
Series' labels to contain names given in SELECT clause.
How to reproduce it (as minimally and precisely as possible):
Just make a query as on the first screenshot.
Anything else we need to know?:
On a dashboard panel, this thing seems to work fine, it's an alert rule that's affected.
Environment:
The text was updated successfully, but these errors were encountered: