Grafana Dashboards for KurrentDB
Run one or more nodes securely as normal with NodePort
set to 2111, 2112, 2113, 2114
Does not have to be in containers.
docker-compose up
Grafana: http://localhost:3000/dashboards admin/admin
Prometheus: http://localhost:9090/
http://localhost:3000/dashboards
When you save the dashboard it will save it to the grafana database but not to the dashboards in the git repository. For that we need to export.
todo: automate!
- open the dashboard in Grafana
- expand/collapse the sections as appropriate
- for the summary dashboard, expand them all
- for the panels dashboard, collapse them all
- set the 'Instance' filter at the top to 'All'
- in the top-right click the
Export
button - click 'Export as JSON'
- set
Export the dashboard to use in another instance
false - Adjust the appropriate dashboard in
./dashboards/
by either clickingDownload file
and replace the file with the new one orCopy to clipboard
and paste over the content of the file
- consider taking some screen shots for
./img
Alternatively, the json in ./dashboards/
can be edited manually.
Note that editing the file in ./dashboards
will cause it to be reimported automatically after a few seconds.
- commit, open a PR, get it merged
todo: automate!
- on the
main
branch - add a git tag (todo: elaborate)
- export for sharing. similar to the internal export except:
- set
Export the dashboard to use in another instance
true Save to file
and use this file for uploading
- set
- upload (todo: elaborate)
- this is not usually necessary, updating to a commit with a different version of the dashboard will cause it to be reimported into the existing database
- docker-compose rm
- delete the data directory (nothing in there is committed)
The json files in ./dashboards
can be edited directly. After a few seconds and a browser refresh they will automatically appear in grafana. PR can then be opened.