Log size in question / refactor log logic
All requests passing through the PROXY are logged in a text file. It contains many information like user, requestTime, RequestLenght, Pre- and PostTreatment, remote address, querystring,...
These are usefull information to make statistics and follow services use.
BUT it needs a lot of storage ressources : we had for example a 300 Mo log file some days ago.
We should consider differents options to redure/optimize log size, like :
- reduce information stored in logs
- have a less verbose logs structure
- compress/aggregate logs
- do not logs some user for instance (admin(monitor users...)
- log only certain type of logEntry (INFO, ERROR, DEBUG, SYSTEM)
#3 Updated by Mérour Xavier over 8 years ago
- Assignee set to Magoni Bruno
The proposal is to add log verbosity options in PROXY backend with the following options :
- silent logging
> no log at all minimal logging > only <LogRequest> nodes are stored (see log structure description) informative logging > only SYSTEM type of logEntries are stored debug logging -> all type of logs are stored (ERROR, SYTEM, INFO, DEBUG)
These options are definable "per connector" (WMS, WMTS, WFS,...).
Bruno, can you add/correct any relevant information about this issue ?
#4 Updated by Mérour Xavier over 8 years ago
I also found some redundant information :
"RemoteResponseToRequestUrl" type in SYSTEM log is the addition of "RemoteRequestUrl" and "RemoteRequest"
Is there any good reason to have it ?
Otherwise, I am not sure to see the difference between "DEBUG" and "INFO" logEntries (there is maybe a good reason...). We may "merge" them in a single logEntry type, no ?
#7 Updated by Magoni Bruno about 8 years ago
- Status changed from New to Accepted
I preconised not to close this task for now as adding log4j support is a transitory step before removing definitively old EasySDI proprietary logs.
I prefer keeping a trace of this before closing current ticket.
Thanks for your feedback.