webappender allow you to visualize the remote logback logs, mapped only to your HTTP request, directly in your browser.
Install the webappender library in your webapp
You have to add to your pom.xml this dependency :
<dependency> <groupId>com.clescot</groupId> <artifactId>webappender</artifactId> <version>1.4</version> </dependency>
A ServletFilter installed via annotation is shipped with the library. Its urlPatterns maps to all requests (
Activate the webappender
By default, webappender is disabled .
Permit to Visualize logs to anyone can be very risky and dangerous in production environments.
So, to prevent any configuration error, we disable by default the webappender. To activate it, you have to put this parameter on the command line launching your application server :
What kind of logs i can visualize ?
webappender, output only logs generated by the thread of your request. It permits to diagnose easily some unit problems, and avoid any interwoven hell from multiple simultaneously requests.
Based on logback, webappender output these informations :
- template arguments
- Mapped Diagnostic Context
- throwable proxy
visualize your logback logs into your firefox browser
when the webappender is shipped in your webapp, and your application server is up, you have to install the fireLogger plugin.
When it's done, hit the F12 key, to visualise the firebug panel ; you should see a new logger panel. It will highlight your logs, according to the level.
Logs are transmitted to your browser, when requests contains a special header forged by the FireLogger plugin :
Visualize your logback logs into your chrome browser
When it's done, hit the F12 key, to visualise the console panel. It will highlight your logs, when you navigate on your webapp.
Logs are transmitted to your browser, when requests contains a special header :
Unfortunately, Chrome logger does not transmit any custom header.
To fix it, you can install another extension like
Visualize your logback logs into any browser
If you cannot install any firefox or chrome plugin, or if you haven't any of these browsers, you can use a body formatter.
You have to :
- transmit to the server a special header :
X-BodyLogger, via an extension like modify headers (chrome or firefox), or any other one compatible with your browser.
- install at the start of your JSP, the taglib declaration, and at the end of your JSP files, the webappender tag . If you use a templating library (like sitemesh for example), an unique insertion into a global decorator can do the job.
<%@ page contentType="text/html;charset=UTF-8" language="java" %> <%@ taglib prefix="debug" uri="https://github.com/clescot/webappender-tag"%> <html> <head> <title>hello from test.jsp page</title> </head> <body> test.jsp </body> </html> <debug:webappender/>
Advantages of this method :
- there are no small size limitations (2Gb seems to be the limit) a chunked response may remove this limitation, but who will have a 2Gb of logs for one request ?
- it works on any browser
Drawbacks of this methods :
- it modifies your body response
- there are no pretty output for these logs
- you cannot filter on the browser-side your logs
Tune log output
Webappender permits to tune the log output, via some specific request headers.
All of them start with the
X-wa prefix, to explain that this option is non standard (X), and specific to the webappender (wa).
If you use firefox, we recommend the modify headers plugin.
Reduce log verbosity
webappender, permits to reduce the verbosity level, to :
- lower the response header overhead
- inactivate time consuming logback display options
To reduce the log verbosity across all browsers, you have to put in your request these header key and value :
This option will not output these expensive log parts (which comes from converters in logback) :
webappender, which actually support logback, support some logback filters, to reduce logs output.
Note that these filters are applied only to the output of the HTTP response, and maps only to logs tied to the request.
Logs are not filtered at start (there are not turboFilters, and appenders configured via the classic way (
logback.xml), view all logs.
Reduce logs with a threshold filter
Logback permits to add a threshold filter, to avoid too many noise in logs.
All logs from a too detailed level will not be output in the webappender.
This filter can be put in place with this kind of header :
Reduce logs with a level filter
Logback permits to add some level filter.
one filter configuration:
two filters configuration :
Reduce logs with a headers size limit
you can add the header 'x-wa-limit-headers-size', with a numeric value, to limit the size of the serialized logs. It will limit the size of the content serialized, before the base64 encoding phase (i.e, the size specified can be 33% lower than the real size serialized). a value lesser than 1 has no effect. This header only works, on ChromeLogger. It means, that if you encounter a too large serialization, which cause an error on the server, and you cannot raise up the limit explained further in this document, you have to put a value lower than your server limit.
Customize logs with an EvaluatorFilter and a JaninoEventEvaluator
Logback permits to add some EvaluatorFilter.
webappender support an EvaluatorFilter bounded with a [JaninoEventEvaluator] (http://logback.qos.ch/manual/filters.html#JaninoEventEvaluator).
To use it, add this custom header :
X-wa-janino-filter=<MATCH/MISMATCH>:<ACCEPT/NEUTRAL/DENY>;expression:your custom expression
For example, you can add this custom header with this related expresion to display only message containing the "3" character :
You also need to add the janino dependency in your pom.xml file :
<dependency> <groupId>org.codehaus.janino</groupId> <artifactId>janino</artifactId> <version>2.6.1</version> </dependency>
More informations on custom expressions in the [JaninoEventEvaluator logback documentation] (http://logback.qos.ch/manual/filters.html#JaninoEventEvaluator).
Test quickly the demo webapp
You can test our super simple demo webapp, to illustrate the features of the webappender library.
Prerequisites of the test
Install the demo
Follow these instructions in your terminal :
git clone firstname.lastname@example.org:clescot/webappender.git cd webappender/webappender-war-example mvn org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:run-war -Dwebappender=true
Test in your browser
Launch your firefox browser, hit the F12 touch to activate firebug, and click on the logger tab. Go to the webapp demo url, and inspect the logger tab.
You will see logs of the demo webapp :
Test the consoleFormatter in your browser
Go to the webapp demo url, and inspect the console tab (hit F12).
Note the additional informations provided on the right panel! when you right-click on a row to display the DOM tab :
If serialized logs are important, you can be faced to two limitations :
- server-side headers limitation
- client-side headers limitation
server-side headers limitation
If logs from your request are huge, your server can throw an exception. To avoid this limit, you can configure your server.
For Tomcat, you can configure your container your HTTP connector with these parameters :
- maxHeaderCount "The maximum number of headers in a request that are allowed by the container. A request that contains more headers than the specified limit will be rejected. A value of less than 0 means no limit. If not specified, a default of 100 is used."
- maxHttpHeaderSize "The maximum size of the request and response HTTP header, specified in bytes. If not specified, this attribute is set to 8192 (8 KB)."
For Jetty, you can configure your container your HTTP connector with these parameters :
- responseHeaderSize "Sets the size of the buffer for response headers. Default is 6K."
client-side headers limitation
Browsers has got some limitations on HTTP headers.
Chrome browser header limit is 250 kb, and 256 kb for all headers. Chrome Logger extension reading logs in only one header, we are limited to 256 Kb.
firefox browser header limit is 10 kb, and 100 Mb or more for all headers. Firelogger extension reading logs in multiple headers, we have no limitations from it.
To overcome these limitations, you can configure some filters to serialize only useful logs from your requests.