Hmmm, did you see
http://www.zenoss.com/product/case-studies/case-study-rackspace/ ?

I'm not sure anyone from rackspace can comment or even reads this forum,
but it seems you can get large device numbers monitored with Zenoss. I
expect it's a lot to do with tuning, and perhaps multiple data
collectors (which isn't simple with Core).

There was a thread about the size of Core installs and the number of
devices monitored, but I'm darned if I can find it now...

I think with 500 windows devices using WMI, you're either going to need
a long cycle time, a really powerful box with 32-64GB RAM and multiple
local collectors, or you'll need to work out (and this isn't easy, or
well explained, but there are some pointers on the Wiki) how to get
distributed collectors working with Core.

Or I'm totally wrong. I don't monitor that many devices with Zenoss as
we're very slowly migrating to it. We've got 57 devices, about 30 of
which are wireless access points.

Finally, if you want a largish install to go easily, I think you'll need
to get some professional help. That might be a consultant, or Zenoss
Enterprise of some flavor.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University



shoa wrote, On 12/11/2008 1:30 PM:

 

 

Sorry for the duplicate subject, it looks like many have dealt with it unsuccessfully in the past...

I am just getting too frustrated, I have made multiple hardware improvements and applied every new release, including 2.3, but I can't get Zenoss up and running, without daemons crashing and UI coming to an unworkable halt... Never mind having a restful night.

The Zenoss idea is the best I have seen, but it just doesn't work.







_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

"jmp242" wrote:

 

http://www.zenoss.com/product/case-studies/case-study-rackspace/ ?

I can provide some general information.

Depending on the number of OIDs you are collecting for those 700 nodes, you may need to go with a distributed model. The important numbers to consider are the number of OIDs being collected and the frequency of your polling. A collector with 8 cores, 32GB of RAM, and 6 15K rpm drives in RAID10 will support around 50,000 OIDs every 5 minutes and will have an average IOWait of around 20%. Much more load than that and we've found that IOWait spikes dramatically and the system becomes unstable/unresponsive. The Zenoss processes themselves don't really require much RAM, but having RAM available for buffering helps you coast through disk IO spikes.

There are some storage tweaks you can apply to squeeze more performance out of the system.
- Monitor the disk usage with an application like IOSTAT or SAR and adjust your RAID controller bias accordingly.
- Mount your /opt/zenoss/perf directory on it's own RAID10 array, and set "noatime" in fstab for that mount
- Mount /opt/zenoss/perf with 'data=writeback' if you are using ext3, you'll get a performance boost but you lose some reliabilty


Hope that helps some. If you can determine the number of OIDs and your polling frequency I may be able to give you a starting point for your hardware.


Chris