![](https://secure.gravatar.com/avatar/3bbbd945c333b8013d0dfa23058f65b9.jpg?s=120&d=mm&r=g)
Yes, this is due to the latest changes. One time, after the update, events would be massive, but then they will appear only if mempools really change.
But this should not happen constantly at every discovery rerun, if this happens, send me output: ./discovery.php -d -m mempools -h <device>
On Thu, Feb 27, 2014 at 9:11 PM, Michael Loftis mloftis@wgops.com wrote:
Is there any way to get the current noise in the event logs from mempool away? Basically every time discovery is run/rerun I get spurious "updated" events for everything. Cisco, Juniper, Dell PowerConnect, and I think Linux, all effected.
2014-02-27 17:08:51sea-1810-c4-c6506MempoolMemory pool updated: type cemp, index 2001.1, descr CPU of Module 3 - Processor 2014-02-27 17:08:51sea-1810-c4-c6506MempoolMemory pool updated: type cemp, index 1001.1, descr CPU of Module 1 - Processor 2014-02-27 17:08:21c3mx.seaMempoolMemory pool updated: type junos, index 9.2.0.0, descr Routing Engine 1 2014-02-27 17:08:21c3mx.seaMempoolMemory pool updated: type junos, index 9.1.0.0, descr Routing Engine 0 2014-02-27 17:08:21c3mx.seaMempoolMemory pool updated: type junos, index 7.11.0.0, descr FPC: DPC 4x 10GE R @ 10/*/*
--
"Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium