I ran into the same problem monitoring my Cisco Firewall. I had to turn the syslog forwarding from my firewall down to error, as all the attempted attack vectors apear to be a level below error.
canito wrote: > > mray wrote: > > I opened http://dev.zenoss.org/trac/ticket/4139 > > > > Thanks, > > Matt Ray > > Zenoss Community Manager > > > Thanks a bunch Matt. But the name look-ups is just one part of the issue. > > The other is the high system resources when syslog, syslog-ng, or any other > syslog application is running concurrent with Zenoss. Zenoss can't handle all > the logs coming from our ASA firewall. I don't know what all information you > need, hence I read ticket 4139 has been solved for this aforementioned issue? -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29399#29399 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
