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

Split dashboard config & state #11382

Closed
RichiH opened this issue Mar 26, 2018 · 4 comments
Closed

Split dashboard config & state #11382

RichiH opened this issue Mar 26, 2018 · 4 comments

Comments

@RichiH
Copy link
Member

RichiH commented Mar 26, 2018

As per IRC with @bergquist and loosely related to #8888 :

It would make sense to split dashboard config (Title, graphs, line width, all those things) from dashboard state (template values, currently selected template value, etc). If the time frame to display is config or state can be debated, but I would lean towards config.

This obviously also ties into #1959 and @bergquist notes that this split would most likely happen after global templates are tackled.

Some more considerations regarding this can also be found in https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

@bergquist bergquist added type/discussion Issue to start a discussion type/feature-request labels Apr 10, 2018
@bergquist bergquist changed the title [FR] Split dashboard config & state Split dashboard config & state Apr 10, 2018
@bergquist
Copy link
Contributor

image

@RichiH
Copy link
Member Author

RichiH commented Apr 10, 2018 via email

@beat
Copy link

beat commented Nov 22, 2018

A way to implement that would be to have sub-dashboards, i.e. dashboards able to display inside a dashboard, and re-use the top-page settings (intervals) and variables from the parent dashboard.

@grafanabot
Copy link
Contributor

This feature request has been open for a long time with few received upvotes or comments, so we are closing it. We're trying to limit open GitHub issues in order to better track planned work and features.

This doesn't mean that we'll never ever implement it or that we will never accept a PR for it. A closed issue can still attract upvotes and act as a ticket to track feature demand/interest.

Thank You to you for taking the time to create this issue!

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

5 participants