-
Notifications
You must be signed in to change notification settings - Fork 24
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
grafana dashboards #664
Comments
@gianlucam76 Can you provide more context about it? I am interested in contributing to the project |
Thanks @ricardocunha. Sveltos add-on controller exposes some metrics on how long it takes to deploy resources per clusters. Like this and this. More can be added (for instance events per clusters or cluster health checks). The idea would be to be a predefined dashboard that Sveltos user can just use to see what is happening. Let me know if this makes sense to you. Thank you! |
I am on this, is it okay if I ask questions when II have them ? |
Actually I'm so confused can you give me more context please ! |
Of course it is OK to ask questions. Create a management cluster and deploy Sveltos (if you have Docker, you can try running the "make quickstart" target from add-on-controller repo, this will create a a management with ClusterAPI and Sveltos and a CAPI cluster with docker as infrastructure provider). Now if you deploy some helm charts or resources, Sveltos will expose some metrics reporting how long it took to deploy those. So if you deploy also Prometheus and Grafana, you can then create a Dashboard where those metrics can be seen. As part of this, on top of creating a dashboard that we can then make it available to Sveltos user, we can also consider which other metrics Sveltos should expose and add those. |
that's super helpful give me a few moments |
I will push my code in a second a DPR, I would appreciate if you could double check ! |
It would be nice to have grafana dashboards to monitor state of add-ons and applications deployment (ClusterSummary.Status)
The text was updated successfully, but these errors were encountered: