Analysis Views of the Workload Monitor
An analysis view is a particular aspect of the workload. Depending on which aspects of the workload you are interested in, you can display various workload parameters, sorted by different sort criteria (such as by users, transaction steps, RFC destinations, and so on).
To activate a particular analysis view, choose the desired view in the 
Analysis Views subscreen by double-clicking it.
The following analysis views are available:
|
Analysis View |
Meaning |
|
Workload distribution for the individual task types |
|
|
Most important performance data for all executed transactions; you can also output the data for summarization levels Packages, Subapplications, or Applications |
|
|
Statistics about workload distribution within a transaction step (activation at transaction level required) |
|
|
Temporal distribution of transaction steps over a day; this allows you to easily identify periods of higher and lower workload |
|
|
The 40 transaction steps with the highest response time and database time; the same hitlists also exist for application statistics |
|
|
Average and maximum memory per dialog step for each transaction and each user |
|
|
Workload caused by Remote Function Calls on the client- and server-side, broken down by transactions, function modules, or destinations |
|
|
|
Workload broken down by users, account numbers, and clients |
|
Volume of data sent and received and the front-end processing times of the individual presentation servers |
|
|
Statistics about the number and volume of spool requests |
|
|
Statistics about the distribution of the response times, showing what percentage of the system requests were dealt with in what time (with or without GUI time) |
|
|
Workload, broken down by table accesses (optional) |
|
|
Workload for a system caused by requests from other systems, broken down by systems, actions, or users |
|
|
Statistics about the called database procedures, optionally broken down by the calling transaction |
|
|
Workload caused by Internet calls, on the client- and server-side, broken down by hosts, transactions, users, or the URL |
|
|
Workload caused by database operations, broken down by the current database connection in each case, or by the calling transaction |
|
|
Workload due to the operation of the VM Container: Resource usage and time usage by VMC actions (Garbage Collection, and so on) |
You can use various analysis views, depending on the user mode you have selected:
|
User Mode |
Service Engineer |
Expert |
|
Possible Analysis Views |
Workload overview Transaction profile Application statistics Time profile Hitlists Memory usage statistics RFC profiles User profile Frontend statistics Response time distribution Load from external systems DB procedure calls Web statistics DB connection statistics |
Workload overview Transaction profile Application statistics Time profile Hitlists Memory usage statistics RFC profiles User profile Account statistics Frontend statistics Spool statistics Response time distribution Load from external systems DB procedure calls Web statistics DB connection statistics VMC Statistics |
Workload Monitor start page