-
Notifications
You must be signed in to change notification settings - Fork 71
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
New module for Prometheus and Grafana Server aka Monitoring Server #1207
Comments
For details on what needs to be done, the documentation is quite clear on what the minion needs - https://documentation.suse.com/suma/4.3/en/suse-manager/administration/monitoring.html |
As Vanda stated, we could have this definition of "done":
|
The manual/ CLI process of installing and configuring Prometheus and Grafana needs to be rethought or updated in the documentation - so the sumaform module is blocked from being worked on until the manual process is updated and tested - https://github.com/SUSE/spacewalk/issues/19714 |
As it's actually a different component of our SUMA/Uyuni architecture, I think it will be good to have the possibility to deploy Monitoring server from Sumaform. So, having a minion module that has on top of it all the related packages/repos and even maybe configured salt formulas that allows us to directly connect and start using a Monitoring server in a deployed sumaform environment.
A simpler approach could be to have an extra flag in our minions, to setup a minion as a Monitoring server. We do something similar to setup them to collect and send Prometheus data through the Prometheus Exporters. But ofc, that would not visually differentiate this different component from the point of view of our architecture.
EDIT after discussion:
Detailed instructions:
The text was updated successfully, but these errors were encountered: