hi all

I would like to you of your opinions or recommendation, of a easy use nagios frontend, i had already tried orean ,nconf, nagiosQL and nagmin docu is not updated anymore for nagios 3.+ vers, but its still a little complicated when adding new hosts or services, I don't really thinks its way faster than adding it to .cfg files on terminal. So if you could help me find a good frontend for my nagios server

Best regards
Nico

Not the easiest to learn but worth it in the end is Centreon - http://www.centreon.com/

You could also look at FAN - http://fannagioscd.sourceforge.net/wordpress/ which is a CentOS based distro configured out the box with Nagios, Centreon and NagVis.

I use this myself with results passed through from three other Nagios instances into a centralised monitoring server.

1 members found this post helpful.

TenTenths , i meant easy to use not "easiest to learn" hehe, by the way thanks for the reply, but i already did centreon, and for me it still take too much time than adding manually in .cfg on terminal, I will try FAN, thanks again

Regards
-Nico

Centreon took a fair bit of time to learn but I just find it so easy to use templates etc. with it. We monitor (at the moment) 300+ services on 65 hosts and it just makes it easy to deal with them through a decent web front-end, plus the graphing is handy too.

hi TenTenths

Thanks again, I had tried Centreon but i really think its not what im looking for, but I really appreciate your reply, I think FAN is nice, ill check the config of adding of new hosts, and monitoring, if its user-friendly, and faster. Ill tell you thanks again

GOD SPEED!!!!

We don't use a front-end, but something that we do that greatly speeds up nagios config is by applying the checks, escalations etc on hostgroups instead of individual hosts.

What this means if I add a new Windows server running IIS and it's role is login servers,
I have to edit
hosts.cfg and copy add 2-3 lines with name, fqdn, alias and hostgroups WINDOWS,IIS,LOGIN,CRITICAL and that's it. All the specific checks are automatically applied to the host for Windows (wsc/disk/cpu/memory etc), IIS (port checks etc), LOGIN (server role specific checks) and CRITICAL (so it escalates to on-call etc), all escalations etc are also automatically applied.