https://monitoring.ovirt.org/nagios/ is public and hosted on the community cage.

Is Icinga not using RAM at all? providing 1GB is totally fine, but it seems a very low requirement compared to Zabbix for example.

OK for CPU

8GB is for Icinga's data I guess? Normally we provide a 8GB system disk and additional storage if needed. So 8+8 IIRC?

I guess there is a public web fontend, so a public IP is needed.

It would replace monitoring.ovirt.org? It seems the web host is serving unrelated things, like the apps tree, maybe we should move this in a proper place.

So it should be fine. Let's add a condition to this for the sake of having a nice infra: the machine should entirely be deployed using Ansible, no manual manipulation )) Hope you're up to the challenge!
(I can give a hand of course)

The version currently in use is:
icinga-1.8.4-4.el6.rf.x86_64

Hardware used:

• 512MB RAM

• 2 vCPU

• 8 GB HDD

@Marc Dequènes (Duck) is there some place in the community cage to host a small VM like this? If yes - we should open a new ticket and move monitoring there. I already have this tested using a VM in PHX but we need something outside the DC for resilience.

I don't think el7 will even install with >1 GB RAM so we can bump the specs up a bit.

After yesterday's community call how should we go ahead with this issue ?

This is is normally done by setting default_user_name=guest in /etc/icinga/cgi.cfg
In our case, however, apache is managing authentication so we can't just skip it.

To avoid this we can add a welcome page to https://monitoring.ovirt.org/ noting the guest user/pass to use. Admins will use their own credentials to manage notifications and other routine stuff in parallel.

Another solution I've done before is to set up a reverse-proxy that would authenticate and display a certain dashboard - this way no auth will be required yet it's much more tricky to do right.