-
Notifications
You must be signed in to change notification settings - Fork 51
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
Set up a Monitoring System #471
Comments
Since I do not recall the context of this I am closing. |
IMHO this is still needed so I've provided context. |
Did you forget to hit send on the comment with the context? |
I modified the original message (from no message to some). |
Discussed during the infra sig: https://community.theforeman.org/t/infrastructure-sig-meeting-notes-2022-01-14/26860#set-up-a-monitoring-systemhttpsgithubcomtheforemanforeman-infraissues471-17 There was a discussion about which system to use. Zabbix was mentioned by @Odilhao while @ekohl mentioned Icinga. The former has the benefit that Odilon has experience with it while the latter has a foreman_monitoring plugin (though a Zabbix backend could be written for smart_proxy_monitoring. It would also run on Netways infrastructure and Netways maintains Icinga. Agreed on the requirements:
|
Icinga/icinga-packaging#283 is blocking us from using Icinga 2. |
Our infrastructure nodes need monitoring. We don't want jobs failing because they Jenkins nodes are running out of disk space. Also notes that are down need to be checked.
The text was updated successfully, but these errors were encountered: