Tom,
Just a couple thoughts to add here...
On Jan 10, 2007, at 10:15 AM, Eric Newton wrote:
number of sites. There are a couple of things I can't seem to find a
lot of information on in the FAQ or Admin Guide, though,
specifically:
We continue to improve the docs each release. :)
1) How well does Zenoss scale across large (10K+ nodes) environments
that are spread across multiple sites? Do you have any performance
numbers for things like parallel service or host checks? Each node
would have multiple checks running against them for different
services
and/or processes.
When you say nodes do you mean a device (ie a piece of hardware
running an OS with interfaces filesystems, etc) or individual
monitors (like a single filesystem check)? We scale the system by
thinking of "devices" which may have many monitors each.
Certainly the system is designed to scale to large numbers and to
that end we can distribute our collectors across multiple machines.
The performance collecting daemons store their data locally (but we
still allow access to the data through one central interface).
The event processing daemons (syslog, snmptrap, win eventlog) can
also be distributed but they send events to a centralized relational
database. This setup can process large numbers of events.
Finally the core configuration database is also central but modeler
daemons can be distributed.
2) Can Zenoss aggregate views from several monitoring servers into an
overall picture (similar to Nagios' distributed monitoring
configuration)? For example, can a site-based monitoring server be
configured to push it's results up to a "master" server somewhere?
The result of the things I describe above is a system that can scale
to large numbers but has one integrated console to view, configure
and manage your information. I think this is a little different than
a distributed nagios setup (although I'm not a nagios expert! :)
-EAD
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
