Global Workload Monitor
Purpose
The Global Workload Monitor (transaction ST03G) displays statistical records for entire landscapes and therefore allows you to analyze statistics data for both ABAP and non-ABAP systems. You can use this data to analyze the workload of the monitored components in great detail. The monitor is organized as a one-screen transaction so that its operation is very intuitive, and so that you can query all desired data with only a few mouse clicks.
While statistics records for an ABAP system can only trace actions that are processed by ABAP-based components, with Distributed Statistics Records (DSRs) you can trace actions that are processed using the non-ABAP components J2EE Engine, ITS, and BC. This also works across component boundaries. Components that write statistics records send data from the statistics record with their communication with other components (their “passport”), meaning that the originator of an action or a data flow of a business process can be traced even beyond component boundaries.
The DSRs are first
stored locally on the relevant component and are transferred to a monitoring
system hourly by
CCMS agents, where
the aggregated statistical data is stored in a performance database and
regularly reorganized.
Integration
·
The operation of
the global workload monitor is largely similar to the operation of the
workload
monitor (transaction ST03), which displays statistical data for the local
ABAP system. The Global Workload Monitor actually uses functions of the
Workload Monitor when you analyze the workload of ABAP systems.
·
The Global Workload
Monitor displays statistical data aggregated by the collector. You can display
raw statistical data (individual records) from ABAP and non-ABAP systems from
complex system landscapes using the
functional trace
(transaction STATTRACE). The functional trace offers a finer resolution. You
can use the functional trace to trace actions that belong to a business
process across system boundaries.
The
differences between the functional trace and the Global Workload Monitor are
explained in the section
Difference Between the
Functional Trace and the Global Workload Monitor.
Features
You can perform the following analyses, among others, in the Global Workload Monitor:
· How is the workload distributed among the individual service types? (For more information about service types, see Displaying the Workload Overview)
· What is the workload of individual actions?
· How is the workload distributed over the individual hours of the day?
· Which action steps have the longest response and wait time?
· What workload data is created when calling external components?
· What is the workload of individual users and which actions has a user performed?
· What workload is created in a component on the basis of actions of external components?
· What is the response time distribution for individual service types (required, for example, for Service Level Agreements)?
· What is the availability of the statistical data for the individual components?
The following applies to all of these analyses:
· You can choose the period for which you want to display data between day, week, and month, or specify the Last Minutes’ Load as you require.
· You can display data for any component or optionally totaled for all components of a type.
See also:
Operating the Global Workload Monitor
Configuring/Self-Monitoring of the Global Workload Monitor