You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
install prometheus with zypper
enable prometheus service
edit the configuration file
restart prometheus service
install grafana with zypper
enable grafana service
Detailed instructions:
The text was updated successfully, but these errors were encountered:
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: