Re: [Nagios-devel] Future of Nagios (was Nagios is dead! Long

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] Future of Nagios (was Nagios is dead! Long

Post by Guest »

I'm not sure why anybody thinks Nagios isn't capable of scaling to =20
anything of that size. I'm currently monitoring almost exactly twice =20=

that (60,000 services/6000 hosts) with 6 hosts and the load on every =20
host is well under .5 (most are .1). The _only_ reason I have so many =20=

monitoring hosts is that the network spans 3 physical locations and I =20=

need some redundancy. I'm even using custom perl scripts for a large =20=

portion of the checks and I haven't needed to even consider using the =20=

embedded perl interpreter yet.

On May 6, 2009, at 12:25 PM, Steven D. Morrey wrote:

> DNX is designed to address pretty much what you're asking for there.
> Being the current lead developer on DNX, I am seeing it handle 3000+ =20=

> hosts and 30,000+ services, all using just 3 boxes and we haven't =20
> even begun to saturate CPU or memory so we know we can go a lot =20
> further.
> You should give it a shot, if you have any questions feel free to =20
> ask us on the dnx list [email protected] (to prevent spam, =20
> sign up is required before posting).
>
> Enjoy!
>
> Sincerely,
> Steve
>
> ________________________________________
> From: Mathieu Gagn=E9 [[email protected]]
> Sent: Wednesday, May 06, 2009 12:33 PM
> To: Nagios Developers List
> Subject: [Nagios-devel] Future of Nagios (was Nagios is dead! Long =20
> live Icinga!)
>
> Hi Ethan,
>
> First, thank you very much for Nagios.
>
> Our enterprise relies heavily on it and Nagios has been a great
> monitoring tools for us for so many years. Up to now, nothing has
> surpassed its simplicity of use and we will continue to use it in the
> foreseeable future.
>
> On 5/6/09 11:56 AM, Ethan Galstad wrote:
>> 4. Big things are coming around the bend for Nagios. Big things take
>> time. Be patient for a bit longer and you'll see the results.
>
> As an enterprise looking to scale Nagios to tens of thousands =20
> monitored
> hosts and services, what could be our expectations of the future
> regarding scalability?
>
> We are using NDOutils to centralize host/service status.
>
> One of our main challenge will be to optimize the configuration and
> patch Nagios/NDOutils to make reloads as fast as possible since =20
> addition
> and removable of monitored hosts have a high turnover rate. (I don't
> know if it's the correct way to say it in English)
>
> Reloading Nagios so it can pickup the new configuration is viewed as a
> "flaw" by our developers team because there's no monitoring done =20
> during
> that time.
>
> If we reload Nagios too often, it would simply pass the majority of =20=

> its
> time exporting configuration/status to NDOutils and scheduling checks
> without doing any real work at all. Too seldom and new monitoring =20
> would
> take too much time before being scheduled.
>
> Any future plan regarding this aspect?
>
> Also, have you ever heard of DNX? http://dnx.sourceforge.net/
> Any future plan about a similar feature within Nagios?
>
> Thanks for your time.
>
> --
> Mathieu
>
> =
--------------------------------------------------------------------------=
----
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! =20=

> Your
> production scanning environment may not be a perfect world - but =20
> thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW =20
> KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
>
> NOTICE: This email message is for the sole use of the intended =20
> recipient(s) and may contain confidential and privileged =20
> information. Any unauthorized review, use, disclosure or =20
> distribution is prohibited. If you are not the intended recipient, =20
> please contact the sender by reply email and destroy all copies of =20
> the original message.
>
>
>
> =
-------------------------------------------------------

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked