Use Case

In the following example, we first analyze the number of log levels displayed in a .LOG file using a pie chart. We then see how to refine the connector configuration to display more relevant data.

This section implies that you are familiar with the Mashup Builder and Administration Console components.

This task shows you how to:

See Also
Logging Framework
Configure the Logs Connector

Step 1: Analyze Log Levels

  1. We want to analyze a .LOG file: configure your connector with the log4j line format.
  2. We want to display a pie chart sorted on log levels:
    1. In the Administration Console, set the log level as category facet in your data model.
    2. In the Mashup Builder, configure a pie chart based on the facet defined previously in your search page.
  3. Reindex.

    You get the following pie chart on your search page:



    Many errors display. Let us see how we can refine our analysis.

Step 2: Group Stack Traces to Refine Analysis

Our log file displays the following error: 

[2014/03/14-14:17:29.129] [error] [1731984037@jtp-adminui-443] [org.eclipse.jetty.servlet.ServletHandler]/
mashup-builder/mashup-ui-proxy/default/staging-builder/BzRVxU6K/downloads:
java.lang.IllegalStateException: STREAM
[2014/03/14-14:17:29.129] [error] [1731984037@jtp-adminui-443] [org.eclipse.jetty.servlet.ServletHandler]at
org.eclipse.jetty.server.Response.getWriter(Response.java:683)
[2014/03/14-14:17:29.129] [error] [1731984037@jtp-adminui-443] [org.eclipse.jetty.servlet.ServletHandler]at
org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:191)
[2014/03/14-14:17:29.129] [error] [1731984037@jtp-adminui-443] [org.eclipse.jetty.servlet.ServletHandler]at
org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:184)
[2014/03/14-14:17:29.129] [error] [1731984037@jtp-adminui-443] [org.eclipse.jetty.servlet.ServletHandler]at
org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:458)
[2014/03/14-14:17:29.129] [error] [1731984037@jtp-adminui-443] [org.eclipse.jetty.servlet.ServletHandler]at
org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:471)
.....

With our current connector configuration, each row containing [error] is analyzed as an error. In this example, we have in fact one single error followed by the details of the exception.

  1. We must configure our connector to ignore the stack trace: in your connector configuration, select Group on for the following fields:
    • date
    • level
    • thread
    • logger
  2. Reindex.

    You get the following pie chart on your search page:



    Rows related to the same error have been grouped.