Skip to content
This repository has been archived by the owner on Feb 4, 2024. It is now read-only.

Latest commit

 

History

History
48 lines (36 loc) · 2.82 KB

why-tracee.md

File metadata and controls

48 lines (36 loc) · 2.82 KB
Raw
layout menu_name title order
docs
Why TracEE?
Why TracEE?
2

In production, logs are still the most reliable source of information which can be used to analyze your application's behavior. In times of microservices and service oriented architecture analyzing of logs is getting more and more complex.

Log aggregation infrastructure like Graylog, Splunk or the Elasticsearch/Logstash/Kibana (ELK) -stack help you to index your logs and search it for interesting information by offering a simple unified user interface.

But there is this one thing that these log aggregators can't help you with - they can't aggregate the log information that belong together on their own.

2014-02-11 15:35:04.127 [tomcat-exec-1] INFO
  my.business.webapp.Servlet - Calling the backend for user Alice now!
2014-02-11 15:35:04.128 [tomcat-exec-2] INFO
  my.business.webapp.Servlet - Calling the backend for user Bob now!
2014-02-11 15:35:05.999 [jboss-exec-15] INFO
  my.business.backend.Service - Everything is fine!
2014-02-11 15:35:05.999 [jboss-exec-21] WARN
  my.business.backend.Service - Something went terribly wrong down here!

Looking at this example, How can you know which user caused the error?

This is where TracEE kicks in. It offers bindings for most popular Java frameworks, that will automatically generate tracking information like invocation or session ids and writes it to your applications log framework contexts. The idea is pretty similar to correlation ids that you manually put into your application APIs to make sense of system interactions - but TracEE solves this for you - automatic and transparent!

Another thing TracEE does is to support passing those ids between all of your components in your application environment, empowering you to gather all log statements that belong to a single invocation, session or other kind of correlation.

Thus using TracEE drastically reduces the time needed for analyzing your systems behavior - for instance in case of an error.

2014-02-11 15:35:04.127 [rxId:BABO sessionId:AFF3] [tomcat-exec-1] INFO
  my.business.webapp.Servlet - Calling the backend for user Alice now!
2014-02-11 15:35:04.128 [rxId:BABA sessionId:EEEE] [tomcat-exec-2] INFO
  my.business.webapp.Servlet - Calling the backend for user Bob now!
2014-02-11 15:35:05.999 [rxId:BABA sessionId:EEEE] [jboss-exec-15] INFO
  my.business.backend.Service - Everything is fine!
2014-02-11 15:35:05.999 [rxId:BABO sessionId:AFF3] [jboss-exec-21] WARN
  my.business.backend.Service - Something went terribly wrong down here!

The integration of TracEE into your application is very easy and doable with almost no effort but adding the TracEE dependencies.

Read the Getting Started and Bindings sections for further details about integrating TracEE into your application.