Hi,

I'm trying to improve my GeoServer logging and I can't see any instructions 
online to deal with the 'Could not find layer' log entries.

If I make an incorrect request for a layer which doesn't exist it generates a 
ServiceException and this includes a log entry which is flagged as an 'ERROR' 
and includes a stack trace with over 100 lines of text. We use OpenLayers so if 
a layer is misconfigured you can get an idea of how much this clogs up the log 
file.

Given that I am using PRODUCTION logging I would like to limit this particular 
log entry to a single line (or two if required). My ideal log entry would be:

"2015-08-17 10:52:49,350 INFO [geoserver.ows] - 
org.geoserver.platform.ServiceException: Could not find layer 
workspace:layername"

I'm aware that others may want it recorded as an ERROR but for me I don't want 
it to do that unless I switch to a different logging level (i.e. DEBUG or 
VERBOSE) for that particular error. To me, this is an incorrect user request it 
is not an actual error in GeoServer; I doubt it is handled in the same way if 
you do a catalog query?

Is there a way to set how particular errors are handled in the logging settings 
or are the settings limited to filtering on error type only?

Thanks,
Paul

"This e-mail is intended for the named addressee(s) only and may contain 
information about individuals or other sensitive information and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this email in error, kindly disregard the 
content of the message and notify the sender immediately. Please be aware that 
all email may be subject to recording and/or monitoring in accordance with 
relevant legislation."
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to