Nagios plain files vs database storage

[yuris]

Hello,

I'm using Nagios for several months with plain files setup, and 
nagiosgrapher. It works pretty nice and I have no problem monitoring ~50 
hosts; ~10 service_checks per host.

Now I'm thinking about migration of other hosts from Zabbix to Nagios 
and totally it is going to be ~350 hosts. Since the number of hosts is 
significant plain test configs does not seem to be a good option, and 
keeping hosts/hostgroups in database seems preferable but from 
experience with Zabbix I know that storing everything in database might 
be not that good idea but pretty obvious bottleneck :/

Could someone please give me an idea what drawbacks I may face if switch 
from plain nagios3 to ndoutils-nagios3-mysql with 350 - 400 hosts ? Can 
I store in mysql db only hosts and hostgroups and manipulate them 
(add/remove) via web interface while keep everything else in old way 
(plain test configs) to reduce load on mysql?

--
wbr,
Yuris

Linux System Engineer,
SMTP.com

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null