Hi Marc (& others that answered my question),
I share your mindset that if using polling 1K instances every 10 seconds
(or so) wouldn't make any sense.
When I post file locking might be an issue, I was not thinking on a pull
mechanism for services (Nagios trying to retrieve information), but in Nagios
being pushed by services for this kind of info. As far as I read from
documentation, for a push schema, the monitored instance has to write a given
file inside Nagios structure to update his status.
What do you think about this?
Regards,
Sebastian
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Powell
Sent: Martes, 10 de Abril de 2007 12:33 p.m.
To: [email protected]
Subject: Re: [Nagios-users] Files locking might be an issue for scalability?
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Sebastian Ganame
> Sent: Tuesday, April 10, 2007 10:13 AM
> To: [email protected]
> Subject: [Nagios-users] Files locking might be an issue for
scalability?
>
> 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.
AFAIK, there is only ever 1 nagios process that writes the status files
at the interval specified by status_update_interval presuming
aggregate_status_updates is enabled, and it should for that many
services. File contention isn't an issue, but how long it takes to
actually write the file might be if you actually want to see
up-to-the-second status information in the web interface.
I personally think you're going to have other scalability issues when
trying to actually perform 10,000 checks every 10 seconds. That's
extremely aggressive IMHO and I believe you'd be breaking new ground.
I'm aware of other installations with that many services but I believe
they're at a more sane check interval of 5 minutes or longer.
--
Marc
-------------------------------------------------------------------------
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
[email protected]
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
---------------------------------
Preguntá. Respondé. Descubrí.
Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
Probalo ya! -------------------------------------------------------------------------
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
[email protected]
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