Add support for dashboard/panel variables in json/jq processor

[Houlistonm]

Our use case has a repeating panel using the traffic light panel and we'd like to pass the variable into the json/jq parser so we can enable the legend and have the name of the application being monitored displayed in the panel. The gojq library support variables here.

Additionally, it would be useful if the http response code was available to the json/jq parser. We are utilizing the new feature to ignore the response code and it's working great when the spring apps are returning a 503. But there are a few conditions where we need to handle a 404, 500, etc. We could wrap the jq parser with an if/else/end to account for the response code if it was available.

[yesoreyeram]

It is already possible. You don't need to pass grafana variables as jq variables. Instead, just use grafana variables syntax in your jq/JSONata query and that will get interpolated automatically

[Houlistonm]

Create a new dashboard, use the table visualization
Create a custom dashboard variable "targets"
values: "a,b,c"
Multivalue: checked
panel options: repeat variable: targets (from pull down)

Query type = json, parser = jq, source = url, format = table, method = get, URL = something that returns json, payload is irrelevant at this time
parsing options: '{"key": ${targets:raw}, "value": 2}'
Returns: error while performing the infinity query. error converting json data to frame: failed to compile jq selector unexpected token "$"

Query type = UQL, source = url, format = table, method = get, url same as above
uql: 'jsonata "{'$targets': 2}" | project kv()'
returns a table with columns key = a, value = 2

The UQL words as you describe, the json/jq does not.
I've tried all variations of quotes, and variable options (json, doublequoted, etc)

[andreygolubkow]

Hi @yesoreyeram ! I have same problem, jq cannot recognise vars, could you put an example please how to use it 🙏

[dg-nvm]

Hi @yesoreyeram , this seems to not be working as the string is parsed to JQ before it's interpolated on the backend, so we are getting the error that there is unexpected token