Chatta subito con l'assistenza
Chat con il supporto

Foglight for PeopleSoft 5.6.11 - User and Reference Guide

Using Foglight for PeopleSoft
Exploring the PeopleSoft Dashboards Foglight for PeopleSoft Agents PS_AppMonitor Agent PS_AppServer Agent PS_DB2SQL Agent PS_MSSQL Agent PS_OracleSQL Agent PS_PPM Agent PS_SchedMonitor Agent PS_SchedServer Agent PS_Scheduler Agent Manual Agent Naming Deployment Scenario Procedures
Foglight for PeopleSoft Reference
Views
PS_AppServer Views PS_DB2SQL Views PS_MSSQL Views PS_OracleSQL Views PS_PPM Views PS_SchedServer Views PS_Scheduler Views
Data

PPM_App_Server_Detail Table View

Purpose
The PPM_App_Server_Detail table view provides metrics for a detailed analysis of PeopleSoft application servers.
 
Table 24. Description of the PPM_App_Server_Detail Table View
Data displayed
•
App Server — Name of the PeopleSoft application server.
•
PMU Count — Number of 100 and 101 PMUs executed during the collection interval.
•
Avg Duration Time(s) — Average execution time for all completed 100 and 101 PMUs at the PeopleSoft enterprise level during the collection period.
•
App Server Load (%) — The processing load consumed by an application server as a percentage of the enterprise-wide processing load. The calculation for App Server Load % is:
•
Load Percentage = server processing load/total processing load for all servers
 
•
Avg PeopleCode Exec Time(s) — Average execution for PeopleCode from completed 400 PMUs per application server during the collection interval.
•
Avg PeopleCode SQL Time(s) — The average time spent executing SQL statements initiated from PeopleCode in a single application server request. This includes the time required for SQL Prepare, Execute, Fetch, and Commit.
The agent calculates this value using metric two from all PMU 400s aggregated to a PeopleSoft application server for the collection interval. This is not the average duration of one SQL statement of this type.
 
•
Avg PeopleCode Built-In SQL Time(s) — The average time spent executing built-in SQL statements in a single application server request per application server during the collection interval. Built-in SQL requests are generated within a PeopleCode built-in function and are executed when that function is called.
The agent calculates this value using metric three from all PMU 400s aggregated to the PeopleSoft enterprise level for the collection interval. This is not the average duration of one SQL statement of this type.
•
Avg PeopleTools SQL Time(s) — The average time spent executing PeopleTools SQL statements in a single application server request per application server during the collection interval. This includes the time required for SQL Prepare, Execute, Fetch, and Commit. PeopleTools SQL statements are all non-PeopleCode and non_Built-in SQL statements executed by the PeopleTools runtime.
The agent calculates this value using metric 4 from all PMU 400s aggregated to a PeopleSoft application server for the collection interval. This is not the average duration of one SQL statement of this type.
•
Avg SQL Exec Count — SQL Execute Count per application server during a collection interval.
•
Avg SQL Fetch Count — Total number of rows fetched from the database per application server during the collection interval.
•
Cache Misses — Manager cache misses resulting in object fetches from the database, aggregated per PeopleSoft application server during the collection interval.
•
File Cache Hits — Manager cache hits resulting in object fetches from file, aggregated per PeopleSoft application server during the collection interval.
•
Mem Cache Hits — Manager cache hits resulting in object fetches from memory, aggregated per PeopleSoft application server during the collection interval.
Where to go next
•
Go to PPM_App_Server_Overview Graph View . This displays a performance overview of the PeopleSoft application servers.
•
Go to PPM_App_Server_Load_Distribution Graph View . This displays the processing load over time of PeopleSoft application servers.

PPM_App_Server_Load_Distribution Graph View

Purpose
The PPM_App_Server_Load_Distribution graph provides the ability to analyze processing load consumed by an application server as a percentage of the enterprise-wide processing load.
Load can be thought of as proportional to the time that a PMU request occupies a server, and therefore, as proportional to duration time. If two users each execute 100 PMU requests in a given time period, they are creating equal system activity, but not necessarily equal load. If the first user performs 100 PMU requests with an average duration time of two seconds, this user's load is 200 seconds. If the second user performs 100 PMU requests with an average duration time of five seconds, this user's load is 500 seconds. As a result, Load Percent provides a quick method to determine an application server's percentage of contribution to the overall load of the PeopleSoft enterprise.
 
Table 25. Description of the PPM_App_Server_Load_Distribution Graph View
Data displayed
•
App Server Load (%) — The processing load consumed by an application server as a percentage of the enterprise-wide processing load. The calculation for App Server Load % is:
•
Load Percentage = server processing load/total processing load for all servers
Where to go next
n/a

PPM_Enterprise_Details Table View

Purpose
The PPM_Enterprise_Details table view provides metrics for a detailed analysis of a PeopleSoft enterprise.
 
Table 26. Description of the PPM_Enterprise_Details Table View
Data displayed
•
PeopleSoft Enterprise Name — Name of the PeopleSoft enterprise.
•
User Count — Number of unique users executing a completed 100 or 101 PMU at the PeopleSoft enterprise level during the collection period.
•
PMU Count — Number of 100 and 101 PMUs executed during the collection interval.
 
•
Avg Duration Time(s) — Average execution time for completed 100 and 101 PMUs at the PeopleSoft enterprise level during the collection period.
•
Web Tier Avg Duration Time(s) — Average execution time for completed PMUs aggregated at the Web server tier level during the collection interval. Web Tier Avg Duration Time is calculated as follows:
•
Total 100 and 101 PMUs minus 400 PMUs containing an associated 100 or 101 PMU/PMU Count.
NOTE: 400 PMUs without an associated 100 or 101 PMU are not included.
•
App Tier Avg Duration Time(s) — Average execution time for completed PMUs aggregated at the Web server tier level during the collection interval. Web Tier Avg Duration Time is calculated as follows:
•
Total 100 and 101 PMUs minus 400 PMUs containing an associated 100 or 101 PMU/PMU Count.
NOTE: 400 PMUs without an associated 100 or 101 PMU are not included.
•
Duration Time Service Level — For the PeopleSoft Enterprise, Duration Time Service Level is the percentage of completed 100 and 101 PMUs that satisfy the threshold for the Duration Time metric specified in the Duration Time Service Level Threshold agent property. This provides the ability to create service level objectives based on duration times for the entire enterprise.
Data displayed
•
Avg PeopleCode SQL Time(s) — The average time spent executing SQL statements initiated from PeopleCode in a single application server request. This includes the time required for SQL Prepare, Execute, Fetch, and Commit.
The agent calculates this value using metric two from all PMU 400s aggregated to the PeopleSoft enterprise level for the collection interval. This is not the average duration of one SQL statement of this type.
•
Avg PeopleCode Built-In SQL Time(s) — The average time spent executing built-in SQL statements in a single application server request. Built-in SQL requests are generated within a PeopleCode built-in function and are executed when that function is called.
The agent calculates this value using metric three from all PMU 400s aggregated to the PeopleSoft enterprise level for the collection interval. This is not the average duration of one SQL statement of this type.
•
Avg PeopleTools SQL Time(s) — The average time spent executing PeopleTools SQL statements in a single application server request. This includes the time required for SQL Prepare, Execute, Fetch, and Commit. PeopleTools SQL statements are all non-PeopleCode and non-built-in SQL statements executed by the PeopleTools runtime.
The agent calculates this value using metric four from all PMU 400s aggregated to the PeopleSoft enterprise level for the collection interval. This is not the average duration of one SQL statement of this type.
•
Duration Time Service Level Threshold(s) — The duration time threshold specified in the Duration Time Service Level Threshold agent property used in calculating the Duration Time Server Level percent.
Where to go next
•
Go to PPM_Enterprise_Duration_Service_Level Graph View . This displays the percentage of PeopleSoft enterprise service level success.
•
Go to PPM_Enterprise_Performance_Overview Graph View .
•
Go to PPM_Enterprise_Duration_Time_Details Table View .

PPM_Enterprise_Duration_Service_Level Graph View

Purpose
The PPM_Enterprise_Duration_Service_Level graph shows the percentage of duration times across the PeopleSoft enterprise that satisfy service level objectives defined through the Duration Time Service Level Threshold.
 
Table 27. Description of the PPM_Enterprise_Duration_Service_Level Graph View
Data displayed
•
Duration Time Service Level — For the PeopleSoft Enterprise, Duration Time Service Level is the percentage of completed 100 and 101 PMUs that satisfy the threshold for the Duration Time metric specified in the Duration Time Service Level Threshold agent property. This provides the ability to create service level objectives based on duration times for the entire enterprise.
Where to go next
Drill down on the Duration Time SL (%) line. For more information, see PPM_Enterprise_Details Table View.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione