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: When using the query builder in the ADX plugin, the template variable of the dashboard cannot be used (like mentioned in the note) because it parses them as a unique string and not as a list of values.
What you expected to happen: Use the template variable also in the builder for a better user experience for users who are not confident with KQL.
How to reproduce it (as minimally and precisely as possible):
Create a template variable for the dashboard
Populate it with some values by which you want to filter in the query
In the ADX Plugin Builder try to use a filter function based on that variable
Run the query
You can see that the clause is translated like | where origin in ('$origin') (adding single quotes around the variable) instead of | where origin in ($origin).
I don't see this as a feature request (even if expected by the documentation) but as a bug, because the Builder itself is the feature for the plugin but it is not working as expected.
Screenshots
Anything else we need to know?:
Environment:
Grafana version: 10.3.4
Plugin version: 4.9.0
OS Grafana is installed on: Azure Managed Grafana
User OS & Browser:
Others:
The text was updated successfully, but these errors were encountered:
What happened: When using the query builder in the ADX plugin, the template variable of the dashboard cannot be used (like mentioned in the note) because it parses them as a unique string and not as a list of values.
What you expected to happen: Use the template variable also in the builder for a better user experience for users who are not confident with KQL.
How to reproduce it (as minimally and precisely as possible):
You can see that the clause is translated like
| where origin in ('$origin')
(adding single quotes around the variable) instead of| where origin in ($origin)
.I don't see this as a feature request (even if expected by the documentation) but as a bug, because the Builder itself is the feature for the plugin but it is not working as expected.
Screenshots
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: