Page History
...
The Entry Points tab includes the following components:
...
| Info |
|---|
The SLA Compliance data can be switched to display as a percentage in the table, or in a ToolTip. |
| Anchor | ||||
|---|---|---|---|---|
|
The Entry Points table displays the following information for the top 30 entry points in the monitored instance:
- Icon - displays . Displays the entry point type.
Name
- displays. Displays the entry point name.
Info
...
Selecting the hyperlinked entry point name selects the entry point in the execution tree and displays the
...
Highlights tab for the entry point.
- Avg. Response Time (Sec) - displays . Displays the average response time for the selected node. The average response time is displayed in seconds.
- Executions - displays . Displays the number of executions within the selected node.
- SLA Compliance - displays . Displays the relative percentage of HTTP entry point service requests that approached or breached the defined SLA thresholds.
- Type - displays . Displays the method type name.
- Sum. Response Times - displays . Displays the total response time for the selected node. The summed response time is displayed in hours: minutes: seconds: milliseconds.
- Avg. Work Time (Sec) - displays . Displays the average actual work time of the selected node without the underlying call path.
- Sum. Work Times - displays . Displays the total work time for the selected node without the underlying call path.
- Max. Response Time (Sec) - displays . Displays the peak response time detected in the selected time frame.
- Min. Response Time (Sec) - displays . Displays the lowest response time detected in the selected time frame.
- Avg. CPU Time (Sec) - displays . Displays the average time that CPU was consumed for the selected node and its underlying call path.
- Sum. CPU Time (Sec) - displays . Displays the total CPU time.
- Max. CPU Time (Sec) - displays . Displays the peak CPU time detected for the selected node.
- CPU Work Impact % - displays . Displays the percent value of the selected node's CPU time out of its entry point's CPU time.
- Avg. CPU Work Time (Sec) - displays . Displays the average actual work time that CPU was consumed for the selected node without its underlying call path.
- Sum. CPU Work Times - displays . Displays the total CPU work time for the selected node without its underlying call path.
| Anchor | ||||
|---|---|---|---|---|
|
The Avg. Response Time (Sec) vs. Executions overtime bar graph displays the relationship over time between the average response time of the entry point selected in the table above and the number of times the entry point was executed in the same time frame. Hovering over any point in the bar graph will display a ToolTip with the date and time of the time slice, the average response time, and the number of executions.
...
The SQL & Exit Points tab displays the following information for all SQLs and exit points in the call tree beneath the selected entity.
...
- Heaviest Exit Points Invoked Directly and Indirectly table
- Avg. Response Time (Sec) vs. Executions overtime bar graph
- Destinations table
The exit points tab can provide information for the following:
- SQL statements
- Exit points methods (each has its relevant type)
- Custom exit points - custom . Custom exit points connect Precise for J2EE to technologies within your environment that Precise cannot directly monitor. Examples are the Documentum Content Server, the Mainframe, etc. Connecting to these technologies, Precise for J2EE can provide you with indepth in-depth information regarding performance bottlenecks seen within your Precise application and pinpoint the root cause from within the external technology. By default, this feature is not configured in Precise for J2EE. For more information regarding enabling and configuring custom exit points, contact Customer Support.
| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
...
When All Instances is the selected top level, this table will be called, Heaviest Exit Points by Work Time - ones that have at least 1% impact on the total. |
The Heaviest Exit Points Invoked Directly and Indirectly table displays the following information for the selected entity:
- Icon - indicates . Indicates the method type or designated entity it represents.
- Name - displays . Displays the exit point name. If the exit point is an SQL, the short SQL text is displayed. If the exit point is a method, the method’s short name is displayed.
- Work Impact - displays . Displays the percentage of work time of the selected exit point in relation to the total work time of the invoking method.
- Avg. Response Time (Sec) - displays . Displays the average response time for the selected node. The average response time is displayed in seconds.
- Executions - displays . Displays the number of executions within the selected node.
- Type - displays . Displays the method type name.
- Sum. Response Times - displays . Displays the total response time for the selected node. The summed response time is displayed in hours: minutes: seconds: milliseconds.
- Max. Response Time (Sec) - displays . Displays the peak response time detected in the selected time frame.
- Min. Response Time (Sec) - displays . Displays the lowest response time detected in the selected time frame.
| Anchor | ||||
|---|---|---|---|---|
|
The Avg. Response Time (Sec) vs. Executions overtime bar graph displays the relationship over time between the average response time of the exit point selected in the table above and the number of times the exit point was executed in the same time frame. Hovering over any point in the bar graph will display a ToolTip with the date and time of the time slice, the average response time, and the number of executions.
| Anchor | ||||
|---|---|---|---|---|
|
The Destinations table displays all destinations for the selected entity:
- Name - displays . Displays the destination name that can be either the Web service request name, 'DB Name' on 'Server Name' for SQLs, and so on.
- Type - displays . Displays the exit point destination type such as, Web service, DB type, and so on.
- Work Impact - displays . Displays the percentage of work time of the selected exit point in relation to the total work time of the invoking method
- Executions - displays . Displays the number of executions within the selected node.
...
The Methods tab includes the following components:
- Methods Invoked Directly and Indirectly
- Avg. Response Time (Sec) vs. Executions for selected method overtime bar graphgraph
| Anchor | ||||
|---|---|---|---|---|
|
On top appears the comparison table called “All Methods Invoked Directly and Indirectly”.
| Info |
|---|
...
This will be Heaviest methods by work time when all instances in the top level in the executions table, with 1% impact min. |
- Icon - displays . Displays the entry point type.
Name
- displays. Displays the entry point name.
Info
...
Selecting the hyperlinked entry point name selects the entry point in the execution tree and displays the Highlights tab for the entry point.
- Work Impact - displays . Displays the percentage of work time of the selected exit point in relation to the total work time of the invoking method
- Avg. Response Time (Sec) - displays . Displays the average response time for the selected node. The average response time is displayed in seconds.
- Executions - displays . Displays the number of executions within the selected node.
- Type - displays . Displays the method type name.
- Sum. Response Times - displays . Displays the total response time for the selected node. The summed response time is displayed in hours: minutes: seconds: milliseconds.Avg. Work Time (Sec) - displays the average actual work time of the selected node without its underlying call path.
- Avg. Work Time (Sec) - displays . Displays the average actual work time of the selected node without the underlying call path.
- Sum. Work Times - displays . Displays the total work time for the selected node without its underlying call path.
- Max. Response Time (Sec) - displays . Displays the peak response time detected in the selected time frame.
- Min. Response Time (Sec) - displays . Displays the lowest response time detected in the selected time frame.
- Avg. CPU Time (Sec) - displays . Displays the average time that CPU was consumed for the selected node and its underlying call path.
- Sum. CPU Times - displays . Displays the total CPU time.
- Max. CPU Time (Sec) - displays . Displays the peak CPU time detected for the selected node.
- CPU Work Impact % - displays . Displays the percent value of the selected node's CPU time out of its entry point's CPU time.
- Avg. CPU Work Time (Sec) - displays . Displays the average actual work time that CPU was consumed for the selected node without its underling call path.
- Sum. CPU Work Times - displays . Displays the total CPU work time for the selected node without its underlying call path.
| Anchor | ||||
|---|---|---|---|---|
|
The Avg. Response Time (Sec) vs. Executions overtime bar graph displays the relationship over time between the average response time of the exit point selected in the table above and the number of times the exit point was executed in the selected time frame. Hovering at any point in the bar graph will display a ToolTip with the date and time of the time slice, the average response time, and the number of executions.
...
The Locks tab also displays the top level URI or iView, or methods (such as: URI, EJB, or others) that are monitored for this instance.Note:
| Info |
|---|
The locking methods themselves are not displayed on the tree. |
The “lock” identifier is calculated at runtime. It is based on the object name that is being locked (synchronized). It is possible to use the same object more than once during the same method. In that case, Precise for J2EE adds an index for each of the lock events, in order to enable the developer to distinguish between the two lock events.
For example:
Public void foo(){//run some code... myLockObjectSynchronized (myLockObject){// will be labeled as myLockObject+0//run some synchronized code...
)//run some more code...// and then we need to have another synchronized block, locking the same object as before
Synchronized (myLockObject){// will be labeled as my LockObject+1
// run some more synchronized code...
)
The Locks tab includes the following components:
...