Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

Dropdown selectors for template variables #349

Closed
mwitkow opened this issue Feb 18, 2015 · 8 comments
Closed

Dropdown selectors for template variables #349

mwitkow opened this issue Feb 18, 2015 · 8 comments

Comments

@mwitkow
Copy link
Contributor

mwitkow commented Feb 18, 2015

It should be possible (e.g. in JSON) to specify expressions that would populate a drop-down selector for a given variable. For example:

I have a dashboard that is parametrised by var.job=web-prod, var.job=web-alpha etc. I have no way for users to discover this,and when they go to a dashboard, they see empty graphs.

Nor is there an easy way to switch between all job names. The job names are already in prometheus data (just list job labels of up{}).

It would be great if JSON allowed me to specify a drop down for this. This would make template variables easily discoverable and give users the ability to see what they can filter by.

@mwitkow
Copy link
Contributor Author

mwitkow commented Mar 2, 2015

We're in dire need of this, and consider implementing hacks to have it.

@juliusv Are you guys thinking about adding selectors for template variables anytime soon?

@stuartnelson3
Copy link
Collaborator

Do you currently have anything in place? You can open a pull request and we will take a look at it

@mwitkow
Copy link
Contributor Author

mwitkow commented Mar 2, 2015

No, we're considering investing time in this, but given that we have little experience with Ruby, it'll probably take a while ;)

@stuartnelson3
Copy link
Collaborator

it would probably be almost entirely javascript, but i'll talk with @juliusv to see what he thinks about it

@mwitkow
Copy link
Contributor Author

mwitkow commented Mar 5, 2015

Any ideas? If you guys don't have the time to implement this, some code pointers as to where to start would be much appreciated :)

@juliusv
Copy link
Contributor

juliusv commented Mar 5, 2015

Hey, I'd just caution against adding fields to the JSON which are not reflected in the GUI. So far the JSON has simply been an internal representation of the settings that you can edit via the GUI. But the JSON is more of an implementation detail. It'd also be great in general to have a UI for this, but that always requires careful thought to not clutter the UI completely for users who don't use that feature. Would love to see some UI sketches for this...

@grobie
Copy link
Contributor

grobie commented Apr 16, 2015

Will come with #378, but first we need to finish #180.

@grobie grobie closed this as completed Apr 16, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants