jamesroman wrote: > You might want to take a look at what devices are filling up your database. I > would log into the events database using the mysql command line client and > issue the following statement: > > mysql -u zenoss -p events > Enter password: > mysql > select DISTINCT device, COUNT(device) as count, severity from > history group by device order by severity, count; > > This will generate a table that tells you how many events each device is > generating and at what severity. You can then focus your efforts on reducing > the number of events created by those devices first, either by configuring > zenoss to ignore more events, or tweaking the client configuration (in my > case the syslog configuration) to reduce the chattiness. I'd look at any > device generating a ton of low severity and a ton of high severity events.
Sorry to necro an old thread, but this may be relevant... I ran the above SQL to investigate my top event-generators, and I find that the Number 1 Offender (by 5x) is 'localhost'... but there is no device named 'localhost', for the Zenoss server itself is listed under it's network name (as has its own count of historical events). So where do I go from here to try to trim these things? I can't even see the event history for this device, since it's not listed. Maybe it's looking at the local syslogs, but I don't know where to start to trim that out. Help? -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=37634#37634 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
