Files locking might be an issue for scalability?

[Andy Shellam]

Hi Sebastian,

I cannot answer from experience I'm afraid, as for me, Nagios only 
monitors a small number of servers.

However there are people on the list who are running with 200, 400, even 
up to 700+ servers, with thousands of services, and Nagios does scale 
reliably.

When you're talking specifically about it's status text files, Nagios 
does have an option (the name escapes me) where it keeps it's status 
data in memory, only writing it to disk every so often, which prevents 
the problem of concurrent writing you're talking about.

Hope this helps some.

Andy.

Sebastian Ganame wrote:
> Hi guys,
> I'm kind of a newbie not only with Nagios, but also with all 
> monitoring/management tools. I’ve just installed Nagios for testing 
> it, and I’m successfully doing basic monitoring of a bunch of 
> subnetworks, with no service monitoring yet (just pinging a few 
> machines, seen how parent/child relationship affects alarming, etc).
> What I need to do is to evaluate if Nagios is suitable for a proof of 
> concept I’m researching on, trying to monitor both hardware and 
> services, and react if needed to meet a defined SLA for Web Services.
> I know that Nagios is able to do this kind of monitoring, but as far 
> as I understood from the documentation, Nagios saves all cache and 
> status of the monitored environment in text files inside the file 
> system, and I was wondering how scalable would this be when trying to 
> online monitor (lets say) 10 services per machine in a 1K machines 
> environment that might update their status every 10 seconds. Do you 
> think text-files locking might be an issue in this case? I cannot 
> found architecture details on Nagios that might answer my question, 
> and maybe some of you can give me an insight on this matter.
> Best regards,
>
> Sebastian Ganame
>
> ------------------------------------------------------------------------
> *Preguntá. Respondé. Descubrí.*
> Todo lo que querías saber, y lo que ni imaginabas,
> está en *Yahoo! Respuestas* (Beta).
> *Probalo ya! <http://ar.answers.yahoo.com>* 
> !DSPAM:37,461baa1d89297748677066!
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> !DSPAM:37,461baa1d89297748677066!
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
>
> !DSPAM:37,461baa1d89297748677066!
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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