J2EE Web Transaction Metrics 

Introduction:

This section is common to all the editions of IT360, as per the below constraints;

• Professional Edition

• Enterprise Edition [Applicable to Probes only, and not applicable / relevant to the Central Server, since the configuration of the monitors happens only at the Probe level. However, you may see these discovered monitors from the Central Server]

• MSP Edition [Applicable to Probes only, and not applicable / relevant to the Central Server, since the configuration of the monitors happens only at the Probe level. However, you may see these discovered monitors from the Central Server]

Monitor Information:

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 the Tree will give you the entire list. Clicking on the respective components, like WEB, will list the various methods of that component alone.

Alert Configuration:

By clicking on the Configure Alert icon, you would be able to configure alerts, based on the following attributes;

• TotalExecution Time

• WebExecution Time

• JavaExecution Time

• JDBCExecution Time

• EJBExecution Time

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

Top

Edit Monitor:

By clicking on the Edit Monitor icon, you would be able to edit the configuration details of the monitor. You can edit the below information;

1. Enter the Display Name of the monitor.

2. Enter the desired Polling Interval. By default it is 10 minutes.

3. Data collection in the Web Transaction Agent can be turned off entirely, by deselecting this option.

4. 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 are collected. For e.g., if the sampling factor is configured as 100, then data will be collected for one, in every 100 executions, of an URL.

5. To control the web transaction agent memory;

   1. 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

   2. Option is given to Include or Exclude specific packages, to be monitored. The agent has to be restarted, for the changes to take effect.

   3. You can choose to enable or disable trace. If you disable the 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;

        Example:

        AccountServlet
           AccountEJB
             . . .
                 Statement.execute

      • You can choose the maximum number of children methods that need to be stored in the Agent;

        Example:

        AccountServlet
        AccountSQL
        .
        .
        .
        Account.JSP

Note: These parameters are used to control the amount of trace that would be stored, and thereby boost the performance of the agent.

Top

See Also:

Creating New Monitor - J2EE Web Transactions Monitor