SpyGlass Tracer can capture execution information at the method and component level and group all data at the transaction level. End to End transactions usually represents system activity from an applicative point of view.

Typical transactions are:

  • Web Application and Web Services invocations at application server level including Servlet, JSP, JSF bean, Struts Actions, Spring controllers and more
  • Message Driven Bean for message management
  • EJB invocations for business logic
  • Scheduled Job

It is possible to extend the definition to any component as Thread execution, listener invocations and more.

A transaction is defined by a URL name and contains information about:

  • method invocations
  • SQL statements
  • exceptions
  • collected data as request parameters, session id, user name, and business variables
  • execution data: execution time, memory usage
  • thread information: thread state and locks

Global statistics as Throughput, Execution Time and Response Level are calculated at the transaction level,

In SpyGlass Tracer a transaction is represented by a Trace object:

The Trace object contains all collected information related to a specific request or execution of the monitored system: