Very true - still way too much traffic. Maybe do something with the dependencies options stuff:
- Would it be possible to just send one "everything is ok" trap for a new overall check? Maybe a new monitor script that queries itself to see if there are any existing problems and will alert based off that? - I'd also continue to send an alert per service if a new service problem is detected. - On the corporate server, I'd setup only setup one service per store entry that would have the "traptimeout" monitor (to watch for the network outages) but still have a service entry for each server to catch any of the specific service outage traps that would be received. That would drop us down to 2400 traps/minute (64kb / sec) + any outages traps. Make sense? Thanks, Tim -----Original Message----- From: David Nolan [mailto:[EMAIL PROTECTED] Sent: Thursday, August 24, 2006 2:40 PM To: Tim Carr; Jim Trocki Cc: mon@linux.kernel.org Subject: RE: Question on Redistribute --On Thursday, August 24, 2006 10:18:56 -0500 Tim Carr <[EMAIL PROTECTED]> wrote: > 4000 traps/second. That sounds like a whole lot to me. Holy cr** thats a lot of traps. Wow, the interesting ways that mon gets deployed continue to amaze me... Even if you were only sending one trap per minute per service you would have: 25 service * 1 trap/minute * 2 servers * 1200 site = 60000 traps/minute, or 1000 traps per second. That still *lot* of traps. Doing your bandwidth math shows that it still 1.6Mbps of trap traffic. I think you might want to make your mon setup more structured, with intermediate collection points that pass status changes only to your final collection point. -David _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
