Anonymous | Login | 2024-11-22 19:59 EST |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0000340 | PacketFence | public | 2008-06-26 10:45 | 2008-09-19 11:49 | ||||
Reporter | rbalzard | |||||||
Assigned To | user4 | |||||||
Priority | normal | Severity | feature | Reproducibility | always | |||
Status | closed | Resolution | fixed | |||||
Platform | OS | OS Version | ||||||
Product Version | ||||||||
Target Version | Fixed in Version | |||||||
Summary | 0000340: use more SNMP log subcategories | |||||||
Description | Right now there are 2 loggers in pfsetvlan: log4perl.rootLogger log4perl.category.pf.SNMP When putting rootLogger to TRACE, the amount of logs is incredibly huge (!!): many Gig in 1 hour. We need to create more sub-categories like pf.SNMP in order to be able to better decide what needs to be logged. Right now, I think there might be: - a category for everything related to lock (including trap parsing, trap handling and trap cleanup) - a category or maybe 2 for trap parsing - a category for trap handling - a category for trap cleanup (post-handling process) - a category for everything related to DB | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
Relationships | ||||||
|
Notes | |
(0000807) user4 2008-09-19 11:49 |
mtn revision 18275056d05b56575429f054d53be6a95c0b170e |
Copyright © 2000 - 2012 MantisBT Group |