This chapter contains the following topics:
This section provides an overview of historical performance data and lists the forms used to analyze historical performance data.
The system stores historical data from the moment a PMU finishes processing or an event occurs. When the archive program runs (R95900/XJDE0002), it either deletes the historical data or moves it to the archive tables.
Analyzing historical data can help you:
Identify trends.
By comparing historical data, you can spot upward and downward performance trends.
Investigate past user complaints.
For example, a user may complain that performance was slow during the previous week. You search historical performance data to find the PMUs that were generated by the user at a specific time a week ago.
| Form Name | FormID | Navigation | Usage |
|---|---|---|---|
| Completed PMUs - Completed PMUs | W95920D | JD Edwards EnterpriseOne Menus, JD Edwards EnterpriseOne Lifecycle Tools, System Administration Tools, JD Edwards EnterpriseOne Performance Monitor, History, Completed PMUs | Enables you to search for and display completed PMUs. |
Access the Completed PMUs - Completed PMUs form.
Before you can view information about completed PMUs, you need to enter criteria so that you can locate the appropriate completed PMUs.
Specifies the code that identifies a user profile.
Categorizes meta-data transaction definitions into a set. Currently, only one definition set exists, and it is reserved for JD Edwards EnterpriseOne development.
Specifies the identifier for a particular PMU you can monitor.
Identifies the name of the trace used to capture performance data that a user can start and stop to capture specific results.
Specifies values (1-3) that are common to the entire user request or a specific tier. PMU metrics contain data specific to an individual PMU.
Identifies each monitored system. JD Edwards EnterpriseOne automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.
Identifies an agent within a domain. This is automatically generated by the monitor the first time an agent registers.
Identifies the duration in milliseconds that a single transaction took to complete.
Identifies the duration in milliseconds that a single transaction took to complete.
Identifies the date and time the monitor started the request. This is related to the duration of a PMU.
Identifies the date and time the monitor started the request. This is related to the duration of a PMU.
At the bottom of the Completed PMUs - Completed PMUs form, the grid contains the information that is related to the PMUs that are retrieved by your search criteria.
You can access the Completed PMUs - PMU Details - C Call Object details form from a variety of JD Edwards EnterpriseOne Performance Monitor forms, such as the Completed PMUs - Completed PMUs form and the Open PMUs - Open PMUs form. You can also access it readily from trees. To access the form, you click the link that is created from the PMU name.
You can access the PMU details form from a variety of JD Edwards EnterpriseOne Performance Monitor forms, such as the Completed PMUs form and the Open PMUs form. You can also access it readily from trees. To access the form, you click the link that is created from the PMU name.
The PMU Details form indicates:
PMU ID and the PMU definition set to which it belongs.
Identification information.
Durations information, including metric values.
Context information.
Additional data.
The information that appears on the PMU Details form varies depending on the type of PMU that is displayed. All metrics are formatted according to information from the metric definition.
Describes a unit of measure that reflects the execution of a section of code.
Identifies the duration in milliseconds that a single transaction took to complete.
Displays completed PMUs in a tree view. Useful to show the hierarchy of nested PMUs. Node description will be the concatenated PMU Label (alternate language if applicable) and PMU duration. Only PMUs that are completed will show. Only top level parents will be displayed at the first level under the root. Children of the parents can be expanded. The PMU selected on the calling form will be set to bold in the tree. The PMU will be shown in the hierarchical context it was created from. Therefore, the selected PMU can be at the parent level or the child level. All nodes can be selected and PMU Detail (W95920F) will be called to show all available information.
Specifies the status the PMU of the PMU.
Specifies the code that identifies a user profile.
Identifies the date and time the monitor started the request. This is related to the duration of a PMU.
Specifies values (1-3) that are common to the entire user request or a specific tier. PMU metrics contain data specific to an individual PMU.
Identifies an agent within a domain. This is automatically generated by the monitor the first time an agent registers with it.
Identifies the name of the trace used to capture performance data that a user can start and stop to capture specific results.
The Context tab reveals the context definition and value that is associated with each PMU in the grid. To view the details of the contexts in a PMU, examine the context and PMU definitions.
This Description column shows data for the additional description value that is part of the incoming PMU. The description stores large character values and generally stores information that exceeds the 128–character limit of Metric 7 and the 254–character limit of the contexts.
The Metrics tab presents the metric values for all of the metrics that are defined for each PMU in the grid.
Metric information appears in a raw format. The values reflect exactly what is stored in the database.
The Additional Data tab enables you to view textual information about the data being captured by the PMU.
The Agent details tab presents information about the agent from which the PMU was executed.
The Identification tab enables you to view specific identifications associated with the PMUs.
A completed PMU can be assigned one of these statuses:
| Status | Description |
|---|---|
| Success | The PMU finished successfully. |
| Failed | The PMU finished unsuccessfully. |
| Abort | Instrumentation code terminated a PMU due to an unexpected condition. |
| Unknown | Assigned in situations when an agent closes a child PMU if the top-level PMU closes out of sequence. |
| Timeout | Instrumentation code timed out the PMU. |
| Reaper Timeout | Long running PMU closed by the Reaper. |
| Admin Timeout | An administrator manually closed the PMU. This is not currently implemented. |