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
When setting possible value of custom templating variable, the UI says Values seperated by comma. However, if we provide the value like a b, c, it will set possible value as a, b, and c instead of a b, and c.
Current we can workaround it by exporting to JSON, modifying, importing from JSON. It would be nicer if we can set it through UI, thanks.
The text was updated successfully, but these errors were encountered:
Why are you having a space in a template variable? graphite and influxdb metric paths do not support space. I could fix it but both space and "," works and others might have taken advantage of the fact that space also works. But I would be happy to make "," the only split char but I would like to know the reason more.
influxdb can use white space as part of its series name, as long as it is quoted or escaped.
Our influxdb is solely used for grafana to display metrics for different customers. We use templating to achieve the goal. A templating variable is used to store customer name. In this configuration, If we list down all possible value of templating variable, we will have an easy to use UI menu for different customer. In order to display customer name in UI menu, we set part of the influxdb series name as customer name. Since customer name contains white space, we have series name containing white space, and templating variable containing white space, too.
When setting possible value of custom templating variable, the UI says
Values seperated by comma
. However, if we provide the value likea b, c
, it will set possible value asa
,b
, andc
instead ofa b
, andc
.Current we can workaround it by exporting to JSON, modifying, importing from JSON. It would be nicer if we can set it through UI, thanks.
The text was updated successfully, but these errors were encountered: