J2EE Web Transaction Metrics

The execution time of the URL and status is displayed along with the performance data for the various components like WEB, EJB, Java and SQL. By clicking on a specific URL, the execution details (Trace) for that particular URL is displayed as a tree structure. The trace will chart the sequence of the internal invocations (methods) of the URL.

In the trace, details of the Methods, like Type of method (Servlet, JSP, JDBC, etc.,) Status of the method (GOOD / ERROR), Execution time is shown. If an SQL is invoked, the SQL Query that was executed would be displayed under More Info. Clicking on Tree will give you the entire list. Clicking on the respective components like WEB will list the various methods of that component alone.

Alarm Configuration:

By clicking on the Configure Alarm icon, you would be able to configure alarms based on the following attributes

TotalExecution Time
WebExecution Time
JavaExecution Time
JDBCExecution Time
EJBExecution Time

You can then associate Thresholds like Response Time and actions like Send Email for the individual URLS, which will be escalated if response time of that particular URL is critical. Know more on alarm configuration. Action can be configured at the monitor level for the Health and Availability. The alarms for a particular URL will be escalated to the monitor.

Note : To update the monitor with current data, click Refresh Data link.

Edit Monitor:

By clicking on the Edit Monitor icon, you would be able to edit the configuration details of the monitor..

Enter the Display Name of the monitor.
Enter the desired Polling Interval. By default it is 10 minutes.
Data collection in the Web Transaction Agent can be turned off entirely, by deselecting this option.
Enter the Sampling Factor. This attribute controls the data collected in the agent. It is the total execution count of an URL after which the statistics is collected. For eg., if the sampling factor is configured as 100 then data will be collected for one in every 100 execution of an URL.
To control the web transaction agent memory
- You can choose the maximum number of URLs whose details are stored in the agent at any given point of time. It would be the set of URLs who have the worst performance i.e., maximum execution time
- Option is given to Include or Exclude specific packages to be monitored. The agent has to be restarted for the changes to take effect.
- You can choose to enable or disable trace. If you disable trace then, only data of the top level transaction is collected.
  - You can choose the maximum depth of methods that need to be stored in the Agent.
    
    For eg.,
    AccountServlet
       AccountEJB
         . . .
             Statement.execute
  - You can choose the maximum number of children methods that need to be stored in the Agent.
    
    For eg.,
    AccountServlet
    AccountSQL
    .
    .
    .
    Account.JSP