-
Notifications
You must be signed in to change notification settings - Fork 1
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
Default dashboards for new installs #99
Comments
@craigdrown @CarlosNZ - suggestions for what to include? |
@mark-prins that list is a good start I think. Thanks. |
Where have you put the ones you've done so far? Should we have a demo dashboard installation that we can collaborate on and then export the JSON to the installer once we're happy with the "package"? Might be able to add some Materialized Views and organise the folder/tagging structure a bit too? |
I've put them in the grafana.db that's in
Yes! The idea was to use demo-board and that has the original defaults. It now needs updating...
Yes, that'd be awesome! |
Sure, I can do that.
Yes, will do.
Yeah, was wondering about that. Are the "Names" the only sensitive data? Like, could you take a client data file and somehow map all the names and their details to a fictional source, would that be enough? I guess also some of the categories and organisations, too. I guess once we had a list of the fields that need to be "protected", it'd be quite straightforward to write a script to replace actual values with fictional equivalents. Sounds like a fun little job. |
I think so, yes. I wondered if it was possible to just update the dates of transactions - there's already a dataset in place, with store and site names changed. Either way would be good - just something to keep the dashboard looking good! |
Would like to have some default dashboards on first install.
The suggestion is to configure a
grafana.db
which would be bundled with our custom installer and this would have an initial setup.Suggestions for boards & panels:
Overview
Stock
Sync Statistics
The text was updated successfully, but these errors were encountered: