Open SqlBenjamin opened 9 months ago
Seems like this might be Azure specific @grafana/partner-datasources
Hi @SqlBenjamin, thank you for opening this. I can confirm I've replicated the problem. It's due to the fact that the \
character is treated as a special character by KQL and requires escaping. Before we can implement a fix for this we'll need to confirm if there are any other characters that may require specific handling.
I'm also transferring this issue to the ADX repo as that's the data source you've referenced. Please let me know if this isn't the case.
What happened?
If I create a variable that is multi value and it has several items selected without a backslash in the values I can reference that variable in KQL queries using an "in" like this:
| where ColumnName in ($VarName)
However, if the column/variable has backslashes this does not work. Nor does using any of the options (that I've tried anyway), such as${VarName:regex}
.I have tried a number of things to try to get this to work but can't seem to figure anything out that would work.
What did you expect to happen?
I would expect to be able to have an easy way to do something like
| where ColumnName in ($VarName)
or| where ColumnName in (${VarName:someoptionhere})
Did this work before?
I don't know.
How do we reproduce it?
Something\1234
,Bob\Loblaw
,Hello\World
would also workTableName | where Column in ($VarName)
(or some other option of that)You can compare to something without a backslash by doing the same steps but using a column with values without a backslash.
Is the bug inside a dashboard panel?
No response
Environment (with versions)?
Grafana: Azure Managed Grafana (version 9.5.16) OS: Windows 11 Browser: Microsoft Edge
Grafana platform?
Other
Datasource(s)?
Azure Data Explorer