...
On the upper right side is a block for time selection, which defines the time interval for displaying collected information and where the user can save specific time intervals.
The rest of the right part layout is a tab-list that is composed of the system information tab, Collector jobs, KPI charts, the KPI mixer, the messages tab, the details tab and the events tab. All these parts and tabs are described in the next sections of this manual.
Figure 
Figure 64: Main GUI layout
Menu buttons
...
Add a new system for monitoring (Shift + F1) – displays a popup window for adding a new system through the defined RFC R/3 connection. The process of adding a new system for monitoring is described in the separate section "Add a new system".
Figure 66
Create new Collector job (F9) – with this button, you can create, assign a profile and start Collector job for the monitoring of system. The process of starting the monitoring is described in a separate section called "Start monitoring".
...
In the system tree, a list of systems and their servers are displayed.
Node in this tree represents a system with a system ID and lists below this node (system) represent its servers with a server name.
For each system, there is additional information in three columns. The "Type" column informs about system type. The event column notifies event occurrence by displaying appropriate icon (meaning of icons is explained in later sections) and the "Last update" column informs when a system was monitored the last time.
Figure 69: Tree list of monitored systems without system groups
The systems could be divided into system groups (folders) wherein one system can be placed in multiple groups.
Figure 70: Tree list of monitored systems with system groups
...
- The system/server is not monitored due to an existing restriction in monitoring which is setup for specific time range, system, server and profile.
Groups in System Pool
It is now possible to organize your systems into groups and sub-groups, based on your preferences.
Right clicking on a group enables you to select or de-select all systems associated with the particular group or select only those systems on which some alerts occur.
Figure 71: Context menu for system pool tree (select all, deselect all, Select all in alert)
...
In the KPI tree, the list of KPIs is divided into logical groups and there are sub-groups in each group. The user may make a specific KPI available in one or more groups and this association can be done in the KPI group maintenance. The maintenance is described in a separate section in this document called "KPI definitions maintenance".
The main group is called 'All KPI'. This group contains all base groups and all KPIs, which are not associated to any Groups.
Figure 72: KPI tree (without / with checkboxes)
...
- Folder context menu - provides functionality to select/deselect all KPIs assigned to this folder and also for its sub-folders. It is useful mainly in the KPI Mix tab, where you can select/unselect KPI nodes.
- KPI context menu - provides default set of functions which can be executed over each KPI. The functionality 'Detail table(s)' is available only when any detail table exist for selected KPI. When not, this functionality is not visible. All functions are explained in next chapter.
...
After the system or server selection, the correlation functionality is executed. This functionality calculates the correlation coeficients for all relevant KPIs which have the same period of collection (e.g. 5 min) and have at least two collected values in the checking time period. Correlation coeficients have the values from the interval < -1;1 >. The closer is the coeficient to the value = abs(1) then more correlating KPI is. By default, only first twenty most correlating KPIs which have the coeficient greater then 0.7, are displayed. The list of all found correlating KPIs are displayed in the KPI Mix tab (when no correlating KPI is found then only selected KPI is displayed in KPI mixer). Also when this functionality is called from another tab, it will automatically redirects the user to the KPI Mix tab.
Set threshold
Set threshold helps the user to create a new alert definition for KPI. When this functionality is selected, pop-up window is displayed in the same screen with preddefined values. The user just have to set a new threshold value (when preddefined values don't need to be changed) and a new alert definition is created in customizing with relevant KPI assignment. All generated alerts in this way have the following naming: X<KPI_NAME(21)><(NUMBER(10)> (e.g. XCPU_LOAD5_PMAX0000000046).
Report Incident
...
- SID – determine system ID for which Collector job has been created.
- Profile – which customizing is in use for the Collector job, i.e. what KPIs is being checked?
- Job status – informs about status of background job of Collector job. Background job can have these statuses:
Not running – No scheduled job.
Scheduled – Job schedule run created for Collector job.
Waiting – Collector job informs that a job is waiting for free work processes for running.
Running - Collector job is currently running.
- Period value / Period type – informs how often a Collector job is running.
Button – If a Collector job is scheduled, the user can click stop button is required which stops and cancels the scheduled job.
Button – If Collector job is not running, the user can click the start button to run the Collector job.- Execution – Determine if Collector job is executed immediately or scheduled on specific date and time.
- Start date/Start time – date and time of initial run of the Collector job.
- Retention time – specifies how old collected data will be stored by Collector job. Data older then retention time are automatically deleted with the exception data, which are collected in saved time intervals.
- Background Job Name/button
– name for background job of Collector job. Clicking on this button will execute transaction SE37 with displaying of this job. - Job last status/Last status icon – specifies about status of last background job run. Can have these statuses:
Finished - specifies that the last background job of Collector job was successfully finished.
Aborted - specifies that the last background job of Collector job was terminated by error or cancelled by user
Not running - specifies that the background job of Collector job was not started before.
- Delay[s] – specifies of any background job delay in seconds while waiting for a free work process.
- Run date/Run time – specifies the date and time in which background job of Collector job is started
- Duration – specifies how long the background job of Collector job was running.
Figure 78: Collector jobs tab
...
Depending on the number of KPIs, these charts are not only placed on one page but on several pages. The user can switch between pages using the 
and 
buttons found on the top left corner of the chart displayed in the KPI tab.
The KPIs, which are displayed in the grid layout, is determined by selected KPI group or specific KPI in KPI tree. Each group consists of KPIs and other subgroups. The correct page is set automatically.
Figure 85: Displaying KPI charts in grid layout by selecting KPI in KPI tree
...
By using the KPI mix tab, the user can see the behaviour of more KPIs together, by graphically comparing dependencies between all measured KPIs, for example, the dependence between the CPU load and work processes.
When the KPI tab is selected, the user may then check to display an active KPI in KPI tree (note that a system/server must also be selected in the system tree). Once a KPI is checked, it will be displayed as a chart of mixed KPIs and assigned to a new coloured series.
When KPI or system/server is unchecked, the appropriate series will be removed from the chart. Allowing the user to create and customize a comparison chart based on individual needs. All KPI series are portioned in the same manner similar to the KPI tab charts specified by KPI definition.
Figure 86: Checked KPI in KPI mixer
...
The messages displayed are dependent on the systems/servers that are checked in the system tree.
Towards the top of the Messages tab, there is a list box in which the user can filter the message group. By default, all messages are displayed and in addition there are the standard ALV operations such as sorting, filtering, aggregating etc.
Figure 87: Monitor Messages
...
This tab contains additional information collected from the monitored systems. All this information of the same kind is categorized and placed into one table. By clicking on a concrete table, all the information is displayed in an ALV list from the table. With this ALV list of messages, it is possible to do all standard ALV operations like sorting, filtering, aggregating and so on.
Figure 88: Detailed information from monitoring
...
With this ALV list of messages, it is possible to do all standard ALV operations like sorting, filtering, aggregating and so on.
For more detailed view on event, just double click on the line in ALV and detailed output will be displayed.
Figure 91: Detail output