Hi Paul,
            You don’t specify what version of GeoServer you’re using, but 
about… 18 months ago?... around 2.5 I think, Warwickshire CC sponsored some 
work to get the logs cleared up a bit. At the time I believe Andrea noted that 
was the first time anyone had done any work cleaning the logs, so if you’re 
using a more recent version then the logs should hopefully have much less 
spurious stuff in them than they used to.

So if you want better logging (and I’m completely with you on that), it may be 
worth “sponsoring” (funding) it. Like WCC, you could get some support which 
includes developer time, it’s cheaper than the proprietary licenses and we 
figured it was a good use of taxpayer money rather than just making the likes 
of ESRI richer (I make such a poor capitalist :) ).

Cheers,
Jonathan

From: Wittle, Paul [mailto:[email protected]]
Sent: Monday, August 17, 2015 11:10 AM
To: [email protected]
Subject: [Geoserver-users] Advanced customisation of GeoServer logging

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."

This message has been scanned for viruses by 
MailControl<http://www.mailcontrol.com/>, a service from BlackSpider Technology

Click 
here<https://www.mailcontrol.com/sr/hVSXevfyRSDGX2PQPOmvUgfUspOYWKRb13JERbrmuf5FaKaS7mD1rFpbxSvrYqgn808agPrDJlGrbIY9K1KtKg==>
 to report this email as spam.



________________________________

HR Wallingford and its subsidiaries uses faxes and emails for confidential and 
legally privileged business communications. They do not of themselves create 
legal commitments. Disclosure to parties other than addressees requires our 
specific consent. We are not liable for unauthorised disclosures nor reliance 
upon them.
If you have received this message in error please advise us immediately and 
destroy all copies of it.

HR Wallingford Limited
Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
Registered in England No. 02562099

________________________________
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to