Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom templating variable cannot contain space #1363

Closed
czchen opened this issue Jan 21, 2015 · 4 comments
Closed

custom templating variable cannot contain space #1363

czchen opened this issue Jan 21, 2015 · 4 comments

Comments

@czchen
Copy link

czchen commented Jan 21, 2015

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.

@torkelo
Copy link
Member

torkelo commented Jan 21, 2015

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.

@czchen
Copy link
Author

czchen commented Jan 21, 2015

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.

@torkelo
Copy link
Member

torkelo commented Jan 23, 2015

Fixed in master

@czchen
Copy link
Author

czchen commented Jan 23, 2015

@torkelo Thanks for the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants