This section includes the following topics:
- About the .NET Activity by CLR portlet
- About the .NET Business View portlet
- About the ASP .NET Activity Over Time portlet
- About the ASP .NET Business View portlet
- About the ASP .NET Top Requests portlet
- About the J2EE Activity by JVM portlet
- About the J2EE Activity Over Time portlet
- About the J2EE Business View portlet
- About the J2EE Load Balancing portlet
- About the J2EE Memory and CPU portlet
- About the J2EE Response Time Breakdown portlet
- About the J2EE Statistic Counter - Data Sources portlet
- About the J2EE Statistic Counter - Overtime Behavior portlet
- About the J2EE Top Entry Points portlet
- About the J2EE Top Execution Types portlet
- About the J2EE Top Methods portlet
- About the J2EE Top SQL and Exit Points portlet
- About the Web Business View portlet
- About the Web Server Activity by Instance portlet
- About the Web Server Activity Over Time portlet
- About the Web Server Top Locations portlet
- About the Web Server Top URLs portlet
- About the Web Top Pages portlet
- About the Web Top Transactions portlet
- About the Web Top Users portlet
About the .NET Activity by CLR portlet
The .NET Activity by CLR portlet displays the .NET activity by CLR in either a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-1 .NET Activity by CLR fields
| Field | Description |
|---|---|
| instance | The name of a process that executes a CLR. Multiple simultaneous executions of the same process on the same server (each with its own CLR) are considered the same instance. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Executions | Displays the number of times a Microsoft ASP.NET service was executed. |
| SLA Breach | Displays the percentage of Microsoft ASP.NET services with SLA settings that did not meet Microsoft ASP.NET services' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Microsoft ASP.NET services with SLA settings that are close to their Microsoft ASP.NET services' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Microsoft ASP.NET services with SLA settings that did meet the Microsoft ASP.NET services' SLA. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the .NET Business View portlet
For information regarding the .NET Business View portlet, see “About the .NET Business View portlet” on page 98.
About the ASP .NET Activity Over Time portlet
The ASP .NET Activity Over Time portlet displays the overtime resource usage of the selected instance.
To view data in this portlet, verify that Precise for Microsoft .NET is installed in the selected application, and that it is integrated with Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-2 ASP.NET Activity Over Time fields
| Field | Description |
|---|---|
| Date and Time | Displays the date and timestamp of the data available in the selected time frame. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Executions | Displays the number of times a Microsoft ASP.NET service was executed. |
| SLA Breach | Displays the percentage of Microsoft ASP.NET services with SLA settings that did not meet Microsoft ASP.NET services' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Microsoft ASP.NET services with SLA settings that are close to their Microsoft ASP.NET services' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Microsoft ASP.NET services with SLA settings that did meet the Microsoft ASP.NET services' SLA. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the ASP .NET Business View portlet
For information regarding the ASP .NET Business View portlet, see “About the ASP .NET Business View portlet” on page 97.
About the ASP .NET Top Requests portlet
The ASP .NET Top Requests portlet displays the top ASP .NET requests either in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for Microsoft .NET is installed in the selected application, and is integrated with Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-3 ASP.NET Top Request fields
| Field | Description |
|---|---|
| Service Request | Displays the top Microsoft ASP.NET service or services. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
Executions | Displays the number of times a Microsoft ASP.NET service was executed. |
| SLA Breach | Displays the percentage of Microsoft ASP.NET services with SLA settings that did not meet Microsoft ASP.NET services' SLAs (as defined by the breach thresholds settings). |
| SLA Near-Breach | Displays the percentage of Microsoft ASP.NET services with SLA settings that are close to their Microsoft ASP.NET services' SLAs (as defined by the near-breach thresholds settings). |
| SLA OK | Displays the percentage of Microsoft ASP.NET services with SLA settings that did meet the Microsoft ASP.NET services' SLA. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the J2EE Activity by JVM portlet
The J2EE Activity by JVM portlet displays the top J2EE activities by JVM in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for J2EE is installed in the selected application, and that it is integrated with Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-4 J2EE Activity by JVM fields
| Field | Description |
|---|---|
| JVM | Displays the name of the monitored instance. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the total processing time of the original J2EE method. |
| Database Times (Summed) | Displays the total processing time of database-related activities (for example, JDBC calls). |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time of the original J2EE method. |
| Database Time (Avg) | Displays the average processing time of database-related activities. |
| Executions | Displays the number of times a J2EE method was executed. |
| SLA Breach | Displays the percentage of executions that exceeded the defined SLA threshold settings. |
| SLA Near-Breach | Displays the percentage of executions that approached the defined SLA threshold settings. |
| SLA OK | Displays the percentage of executions that did not meet the defined SLA threshold settings. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the J2EE Activity Over Time portlet
The J2EE Activity Over Time portlet displays the overtime resource usage of the selected instance.
To view data in this portlet, verify that Precise for J2EE is installed in the selected application, and that it is integrated with Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-5 J2EE Activity Over Time fields
| Field | Description |
|---|---|
| Date and Time | Displays the date and timestamp of the data available in the selected time frame. |
| Response Times (Summed) | Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Times (Summed) | Displays the sum of the processing time of the original J2EE method. |
| Database Times (Summed) | Displays the sum of the processing time of database-related activities (for example, JDBC calls). |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Work Time (Avg) | Displays the average processing time of the original J2EE method. |
| Database Time (Avg) | Displays the average processing time of database-related activities. |
Executions | Displays the number of times a J2EE method was executed. |
| SLA Breach | Displays the percentage of executions that exceeded the defined SLA threshold settings. |
| SLA Near-Breach | Displays the percentage of executions that approached the defined SLA threshold settings. |
| SLA OK | Displays the percentage of executions that did not meet the defined SLA threshold settings. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the J2EE Business View portlet
For information regarding the J2EE Business View portlet, see “About the J2EE Business View portlet” on page 96.
About the J2EE Load Balancing portlet
This portlet works with Precise v9.0 or higher.
The J2EE Load Balancing portlet displays the J2EE load balancing in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
The following table describes the fields displayed in this portlet.
Table 7-6 J2EE Load Balancing fields
| Field | Description |
|---|---|
| Status | Displays the monitoring status of the instance. |
| Instance | Displays the name of the instance. |
| Server | Displays the name of the server. |
| Response Time (Avg) | Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side. |
| Executions | Displays the number of times the instance was executed. |
| Avg. Memory (Bytes) | Displays the instance’s average memory consumption. |
| CPU (%) | Displays the instance’s relative CPU consumption rate. |
| Availability | Displays the instance’s availability rate. |
| SLA Breach | Displays the percentage of executions that exceeded the defined SLA threshold settings. |
| SLA Near-Breach | Displays the percentage of executions that approached the defined SLA threshold settings. |
| SLA OK | Displays the percentage of executions that did not meet the defined SLA threshold settings. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the J2EE Memory and CPU portlet
This portlet works with Precise v9.0 or higher.
The J2EE Memory and CPU portlet displays the memory used in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources. The following table describes the fields displayed in this portlet.
Table 7-7 J2EE Memory and CPU fields
| Field | Description |
|---|---|
| Time | Displays the time frame in which the performance data was collected. |
| Used Heap | Displays the heap used in the selected time frame. |
| Total Allocated Heap | Displays the total byte value of heap allocated to the selected instance or all instances. |
| Maximum Allowed Heap Size | Displays the top threshold of heap allocated to the selected instance or all instances. |
| Maximum Used Heap | Displays the amount of heap used at the highest point of heap consumption. |
| Minimum Used Heap | Displays the amount of heap used at the lowest point of heap consumption. |
| Major Garbage Collection (%) | Displays the relative time spent in garbage collection in the selected time frame. |
| CPU Consumption | Displays the relative CPU consumption in the selected time frame. |
See “About the Tools portlets” on page 30, “Configuring the portlet” on page 33, and “Defining the portlet data preferences” on page 34.
About the J2EE Response Time Breakdown portlet
This portlet works with Precise v9.0 or higher.
The J2EE Response Time Breakdown portlet displays the average response time in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
The following table describes the fields displayed in this portlet.
Table 7-8 J2EE Response Time Breakdown fields
Field Description
TIme Displays the time frame in which the presented performance data was collected.
HTTP Displays the relative average response time spent executing HTTP requests.
Struts Displays the relative average response time spent executing Struts requests.
Spring Displays the relative average response time spent executing Spring requests.
EJB Displays the relative average response time spent executing EJB requests.
Lock Displays the relative average response time spent in lock.
Hibernated/JPA Displays the relative average response time spent executing Hibernated/JPA requests.
JDBC Displays the relative average response time spent executing JDBC requests.
Web Service Displays the relative average response time spent executing Web Service requests.
RMI Displays the relative average response time spent executing RMI requests.
SAP RFC Displays the relative average response time spent executing SAP RFC requests.
Tuxedo Displays the relative average response time spent executing Tuxedo requests.
Custom Displays the relative average response time spent executing user-defined method requests.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the J2EE Statistic Counter - Data Sources portlet
This portlet works with Precise v9.0 or higher.
The J2EE Statistic Counter - Data Sources portlet displays the J2EE category in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
The following table describes the fields displayed in this portlet.
Table 7-9 J2EE Statistic Counter - Data Sources fields
Field Description
Data Source Name of the Data Source.
Min Value Displays the minimum value of performance statistics
Avg Value Displays the average value of performance statistics.
Max Value Displays the maximum value of performance statistics.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the J2EE Statistic Counter - Overtime Behavior portlet
This portlet works with Precise v9.0 or higher.
The J2EE Statistic Counter - Overtime Behavior portlet displays the overtime resource usage of the selected server. The following table describes the fields displayed in this portlet.
Table 7-10 J2EE Statistic Counter - Overtime Behavior fields
Field Description
Time Displays the time frame in which the presented performance data was collected.
Avg Value Displays the average value of performance statistics.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the J2EE Top Entry Points portlet
This portlet works with Precise v9.0 or higher.
The J2EE Top Entry Points portlet displays the top J2EE entry points in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
The following table describes the fields displayed in this portlet.
Table 7-11 J2EE Top Entry Points fields
Field Description
Name Displays name of the instance.
Avg. Response Time (Sec) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Executions Displays the amount of executions of the instance.
Type Displays the entry point type (e.g. HTTP, Custom)
SLA Breach Displays the percentage of executions that exceeded the defined SLA threshold settings.
SLA Near-Breach Displays the percentage of executions that approached the defined SLA threshold settings.
SLA OK Displays the percentage of executions that did not meet the defined SLA threshold settings.
Sum. Response Times Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Sum. Work Times Displays the sum of the processing time of the original J2EE method.
Max. Response Time (Sec) Displays the maximum time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Sum. CPU Time Displays the aggregated CPU time recorded in the selected time frame.
Max. CPU Time (Sec) Displays the highest CPU time recorded in the selected time frame.
Sum. CPU Work Times Displays the aggregated CPU work time recorded in the selected time frame.
Avg. Work Time (Sec) Displays the average work time for the selected time frame.
Min. Response Time (Sec) Displays the minimum time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Avg. CPU Time (Sec) Displays the average CPU time for all entry points in the selected time frame.
Avg. CPU Work Time (Sec) Displays the average CPU work time for all entry points in the selected time frame.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the J2EE Top Execution Types portlet
The J2EE Top Execution Types portlet displays the top J2EE execution types in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for J2EE is installed in the selected application, and that it is integrated with Insight.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their cause.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-12 J2EE Top Execution Types fields
Field Description
Type Displays the top J2EE execution types.
Response Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Work Times (Summed) Displays the sum of the processing time of the original J2EE method.
Database Times (Summed) Displays the sum of the processing time of database-related activities (for example, JDBC calls).
Response Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Work Time (Avg) Displays the average processing time of the original J2EE method.
Database Time (Avg) Displays the average processing time of database-related activities.
Executions Displays the number of times a J2EE method was executed.
SLA Breach Displays the percentage of executions that exceeded the defined SLA threshold settings.
SLA Near-Breach Displays the percentage of executions that approached the defined SLA threshold settings.
SLA OK Displays the percentage of executions that did not meet the defined SLA threshold settings.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the J2EE Top Methods portlet
The J2EE Top Methods portlet displays the top J2EE methods in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
To view data in this portlet, verify that Precise for J2EE is installed in the selected application, and that it is integrated with PMDB and Insight.
When the chosen application is v8.x, the configuration screen of this portlet is different than when your chosen application is v9.0 or higher.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-13 J2EE Top Method Execution fields
Field Description
Method Execution Displays the top J2EE method execution or executions.
Response Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Work Times (Summed) Displays the sum of the processing time of the original J2EE method.
Execution Times (Summed) Summarizes the time that executed elements contributed to the original J2EE method response time. For example, an internally executed Servlet or JSP, an EJB call, or a JDBC call, contribute to the method response time.
Database Times (Summed) Displays the sum of the processing time of database-related activities (for example, JDBC calls).
Response Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Work Time (Avg) Displays the average processing time of the original J2EE method.
Execution Time (Avg) Displays the average time that executed elements contributed to the original J2EE method response time.
Database Time (Avg) Displays the average processing time of database-related activities.
Executions Displays the number of times a J2EE method was executed.
SLA Breach Displays the percentage of executions that exceeded the defined SLA threshold settings.
SLA Near-Breach Displays the percentage of executions that approached the defined SLA threshold settings.
SLA OK Displays the percentage of executions that did not meet the defined SLA threshold settings.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the J2EE Top SQL and Exit Points portlet
This portlet works with Precise v9.0 or higher.
The J2EE Top SQL and Exit Points portlet displays the top J2EE SQL and exit points in a selected instance or in all instances in the selected Tier. This view easily identifies the programs consuming the most resources.
The following table describes the fields displayed in this portlet.
Table 7-14 J2EE Top SQL and Exit Points fields
Field Description
Name Displays the name of the SQL or exit point.
Work Impact (%) Displays the relative
Avg. Response Time (Sec) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Executions Displays the number of times the SQL or exit point was executed.
Type Displays the SQL or exit point type.
Sum. Response Times Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Max. Response Time (Sec) Displays the maximum time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Min. Response Time (Sec) Displays the minimum time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Business View portlet
For information regarding the Web Business View portlet, see “About the Web Business View portlet” on page 96.
About the Web Server Activity by Instance portlet
The Web Server Activity by Instance portlet displays the Web server activity by instance in the selected Tier. This view easily identifies the instances consuming the most resources.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-15 Web Server Activity by Instance fields
Field Description
Instance Displays the name of Web instances included in the same application.
Response+Network Times (Summed) Displays the total response and network time.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Response+Network Time (Avg) Displays the average response and network time.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective, sampled during the selected time frame. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web URL.
SLA Breach Displays the percentage of Web URLs with SLA settings that did not meet their SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of Web URLs with SLA settings that are close to their SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of Web URLs with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Server Activity Over Time portlet
The Web Server Activity Over Time displays the overtime resource usage of the selected instance. To view data in this portlet, verify that a Web server is installed in the selected application.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-16 Web Server Activity Over Time fields
Field Description
Date and Time Displays the date and timestamp of the data available in the selected time frame.
Response+Network Times (Summed) Displays the total response and network time.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Response+Network Time (Avg) Displays the average response and network time.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective, sampled during the selected time frame. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web URL.
SLA Breach Displays the percentage of Web URLs with SLA settings that did not meet their SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of Web URLs with SLA settings that are close to their SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of Web URLs with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Server Top Locations portlet
The Web Server Top Locations portlet displays the top Web server locations in a selected instance or in all instances in the selected Tier. This view easily identifies the instances consuming the most resources.
To view data in this portlet, verify that a Web server is installed in the selected application.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-17 Web Server Top Locations fields
Field Description
Location Displays the name (configured in Precise) of a Network subnet or a group of client IPs.
Service + Network Times (Summed) Displays total service and network time, including the total amount of time the request took to reach the server.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Service + Network Time (Avg) Displays the average service and network time, including the average amount of time the request took to reach the server.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web Server location.
SLA Breach Displays the percentage of Web Server locations with SLA settings that did not meet their
SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of Web Server locations with SLA settings that are close to their
SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of Web Server locations with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Server Top URLs portlet
The Web Server Top URLs portlet displays the top Web server URLs in a selected instance or in all instances in the selected Tier. This view easily identifies the instances consuming the most resources.
To view data in this portlet, verify that a Web server is installed in the selected application.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-18 Web Server Top URL fields
Field Description
URL Displays the top Web server-side URLs.
Response+Network Times (Summed) Displays the total response and network time.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Response+Network Time (Avg) Displays the average response and network time.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web URL.
SLA Breach Displays the percentage of top Web server-side URLs with SLA settings that did not meet their SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of top Web server-side URLs with SLA settings that are close to their SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of top Web server-side URLs with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Top Pages portlet
The Web Top Pages portlet displays the top Web pages in a selected instance or in all instances in the selected Tier. This view easily identifies the instances consuming the most resources. Selecting a page name launches Precise for Web in context.
To view data in this portlet, verify that a Web server is installed in the selected application.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-19 Web Top Pages fields
Field Description
Location Displays the name (configured in Precise) of a Network subnet or a group of client IPs.
Service + Network Times (Summed) Displays total service and network time, including the total amount of time the request took to reach the server.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Service + Network Time (Avg) Displays the average service and network time, including the average amount of time the request took to reach the server.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web Server location.
SLA Breach Displays the percentage of Web Server locations with SLA settings that did not meet their
SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of Web Server locations with SLA settings that are close to their
SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of Web Server locations with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Top Transactions portlet
The Web Top Transactions portlet displays the top Web transactions in a selected instance or in all instances in the selected Tier. This view easily identifies the instances consuming the most resources. Selecting a page name launches Precise for Web in context.
To view data in this portlet, verify that a Web server is installed in the selected application.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-20 Web Top Transactions fields
Field Description
Location Displays the name (configured in Precise) of a Network subnet or a group of client IPs.
Service + Network Times (Summed) Displays total service and network time, including the total amount of time the request took to reach the server.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Service + Network Time (Avg) Displays the average service and network time, including the average amount of time the request took to reach the server.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web Server location.
SLA Breach Displays the percentage of Web Server locations with SLA settings that did not meet their
SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of Web Server locations with SLA settings that are close to their
SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of Web Server locations with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.
About the Web Top Users portlet
The Web Top Users portlet displays the top Web users in a selected instance or in all instances in the selected Tier. This view easily identifies the instances consuming the most resources. Selecting a page name launches Precise for Web in context.
To view data in this portlet, verify that a Web server is installed in the selected application.
An SLA (Service Level Agreement) is a formal definition of an information system's performance goals. Within Precise, an SLA consists of clauses corresponding to various system activities. After you define a system's SLA, you can analyze SLA compliance and isolate breaches to identify their causes.
Poor service is the sum of the SLA Breach and SLA Near-Breach counters.
The following table describes the fields displayed in this portlet.
Table 7-21 Web Top Users fields
Field Description
URL Displays the top Web server-side URLs.
Response+Network Times (Summed) Displays the total response and network time.
Work Times (Summed) Displays the elapsed time from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Times (Summed) Displays the time spent on network activity from the server-side perspective. This includes the time to read the request from the network and the time to send the response back to the client through the network.
Response+Network Time (Avg) Displays the average response and network time.
Work Time (Avg) Displays the average time that elapsed from when a request is received by the server to the time a response is sent back to the computer that made the request. The response time is measured on the server-side.
Network Time (Avg) Displays the average time spent on network activity from the server-side perspective. This includes the average time it took to read the request from the network and the average time it took to send the response back to the client through the network.
Executions Displays the number of HTTP requests received for a Web URL.
SLA Breach Displays the percentage of top Web server-side URLs with SLA settings that did not meet their SLAs (as defined in the breach threshold settings).
SLA Near-Breach Displays the percentage of top Web server-side URLs with SLA settings that are close to their SLAs (as defined in the near-breach threshold settings).
SLA OK Displays the percentage of top Web server-side URLs with SLA settings that did meet their SLAs.
See “About the Tools portlets” on page 30. See “Configuring the portlet” on page 33.
See “Defining the portlet data preferences” on page 34.