Viewing Top PeopleCode Events
Access the Top PeopleCode Events page (PeopleTools, Performance Monitor, Analytics, Top PeopleCode Events).
These charts show the PeopleCode events that have highest durations and execution counts, grouped by component and event type. Durations and counts are summed across levels (record field, component record, page and component) for each component and event type.
All charts have a View in Grid hyperlink to show the chart information in a grid. This also enables users to sort the information and to download to Microsoft Excel spreadsheets.
Note: Performance data must be captured in verbose agent filter mode or higher to be displayed.
Before you can view PeopleCode events, you must first enter search criteria.
Field or Control
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.
The user ID of the user who generated the request.
The User ID field prompts against the PSPMOPRDEFN table, which is populated by the Lookup program (PSPM_LOOKUP).
|Performance Trace Name||
You enter the performance trace name to search on PMUs within a particular performance trace. If a user has launched a performance trace in the Performance Console, the system labels every PMU that is generated in a business process with a performance trace name.
Performance Trace Name prompts against the PSPMPERFTRACE table, which is populated by the Lookup program (PSPM_LOOKUP).
Note: When searching using a performance trace name, the search ignores all agent IDs, so the current system ID is not relevant.
Select the component name.
Select the market to which the component belongs.
Specify a range of time. The system searches on the monitor date and time, not the agent date and time. If you do not specify a time range, by default, the system displays information for the current day, starting at midnight (12:00 AM).
The Search button performs a search based on the search criteria that is defined on the page. It should be pressed only once per search. 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.
|Number to Retrieve||
The number of top ranked statistics to be displayed on the charts.
Updates the To Time value to equal the current time. Enables you to view the most current results of a search.
Note: If the filter level of the PSAPPSRV agent type is set to a level that is lower than the level of PMU 500–516 (Verbose), a warning message appears at the top of the page indicating that information for the current component may not be available. This data is available only in the following situations: the agent filters on the application server are set to verbose or debug, or performance traces were run with a filter level set to debug or verbose. A small, yellow triangle appears at the top of the page alerting you if application servers for that system are currently at a higher filter level than verbose. This, however, does not mean that you would not see data; PMUs may exist from performance traces or lower filter levels from past monitoring.
Top PeopleCode Events
This chart indicates the PeopleCode events that are run most often.
It shows the highest counts for all PMU 500–516. The counts consist of adding metrics 1, 3, and 5. The data is grouped by component and event name (contexts 1 and 2).
Top Cumulative Durations
This chart reveals the largest sum of all the durations of a specific PeopleCode event.
It shows the top sum of PMU 500–516 durations. The duration is not the duration of the PMU; the duration is the sum of metrics 2, 4, and 6. The data is grouped by component and event name (contexts 1 and 2).
This chart shows the components with event types that on average consume the most time in application server requests.
Duration averages are the averages and standard deviations of the sum of durations of PMU 500–516. The duration is not the duration of the PMU; the duration is the sum of metrics 2, 4, and 6. The data is grouped by component and event name (contexts 1 and 2). The sample count that is used to calculate these averages is not the execution counts of the events (metrics 1, 3 and 5) but the number of times this component reported that event type.