Viewing Completed PMUs

Identifies each monitored system. PeopleSoft automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.

The name of the PeopleSoft application database running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.

If you want information for a particular user, enter the user ID of the user for which you want to track completed PMUs.

This field prompts against the PSPMOPRDEFN table.

Enables you to search completed PMUs by the process ID.

If a user has launched a performance trace in the Performance Trace Console, the system labels every PMU that is generated in a business process with a performance trace name. Select the appropriate trace name to view its results.

The Performance Trace Name field prompts against the PSPMPERFTRACE table, which the Lookup program (PSPM_LOOKUP) populates.

If you want information for a particular component, enter the name of the component for which you want to track completed PMUs.

This field prompts against the PSPMPNLGRPDEFN table.

Enter the market that is associated with the component.

Indicates the set to which the PMU definition belongs. A PMU definition set is similar to a message set.

This is required if you want to generate metric and duration charts.

Identifies the PMU definition within a PMU definition set.

This is required if you want to generate metric and duration charts.

PMU metrics contain data that is specific to that PMU. Context values, on the other hand, are common to the entire user request or a specific tier. For example, the component name is stored in a context. The system uses contexts to "flatten" a PMU tree. For example, you do not have to navigate up from a SQL PMU to an ICPanel PMU to see what component generated that SQL statement. In some cases, PMU types are shared across different user request types. In such cases, the label for the PMU will be generic. Use the Context Help button to view the context definitions for a PMU set ID and ID that you've entered.

Displays the PMU status.

See Completed PMU Status.

Each PMU that is reported by an agent has a unique instance ID. The instance identifier of the first PMU generated by a particular user request is the top instance. The value of the top instance is then stored with every child PMU within a request. The top instance is the associating value for all PMUs that are generated by the same user request.

This search field applies only when you are searching for PeopleCode SQL PMUs, which are PMU 406 (PeopleCode SQL Execute) and PMU 407 (PeopleCode BuiltIn SQL Execute). The Context 2 field contains the PeopleCode program name andMetric 2 contains the statement number in the PeopleCode where the SQL was executed.

To search by statement number, you must enter the following search criteria: PMU Definition Set = 1, PMU ID = 406 or 407, and Context 2 must have the name of a PeopleCode program.

Specify a range of time in which the system should search for completed PMUs.

The system searches on the monitor date and time, not the agent date and time.

Specify criteria that is related to the duration of a PMU in milliseconds.

Select the application server domain to generate the PMUs.

Select the name and port number of the server machine on which the domain that generated the PMU resides.

Identify the specific agent that monitored a PMU.

Identify the type of agent that monitored a PMU.

The Search button performs a search based on the search criteria that is defined on the page. If you want to view the most current information, use theRefresh button after running the initial search. If you clickSearch repeatedly, the system returns the same results from the same time range for each search.

Updates the value in the To Time field to equal the current time and performs a search. This enables you to view the most current results of a search.