System tree

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}

Each node of type system or server can be selected and checked. For the selected node, (only one can be selected at a time), the relevant information is always displayed in the first tab "System info".
For all checked nodes, all information is displayed for the appropriate/selected KPIs, messages, events and detailed information in the other tabs.
If the node of this tree is greyed out, then this means that it is inactive. This status means that for this system and server and for the selected time interval, no information is collected. Inactive node can be selected but not checked.
Each node of system and the server has an information status icon, which informs about the current state of monitoring.
This icon may have these statuses:

- At least One Collector job is executed for the system, which indicates that a background job for this Collector job is currently running for collection of KPIs.

- At least One Collector job is due to be executed on the system, so the background job for this Collector job is released and once a free process is available, it will be executed.

- At least One Collector job failed in last run on the system, so the background job of this Collector job has been aborted or cancelled.

- System is monitored by at least one scheduled Collector job and previous execution of Collector job was carried out successfully for this system.

- System is not reachable through the RFC connection, this could because, for example, the system is not responding or RFC connection is not valid anymore.
- System is not monitored because no monitoring of Collector job is started.
- The server of monitored system is excluded from monitoring; therefore, the accessibility of this server is not checked.

- 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 group or select only those systems with present alerts or alerts which were occurring in the past for a chosen time period.

Figure 71: Context menu for system pool tree (select all, deselect all, Select all in alert, Select all in alert for time range )

KPI tree

In the KPI tree, the list of KPIs is divided into logical groups and each group can contain subgroups. You can add a specific KPI to one or more groups by clicking on the button in the toolbar, which navigates you into the KPI group maintenance. The KPI maintenance is described in a separate section under /wiki/spaces/ITOA/pages/4474634314.

The main group in the KPI tree is called All KPI. This group contains all base groups and all KPIs, which aren't associated to any group.

_{Figure 72: KPI tree}

Nodes in a KPI tree have either an active or an inactive status. A KPI node is inactive, when the KPI values for the selected systems and servers, weren't measured in a selected time interval. Inactive KPI group node occurs, when all KPIs are inactive in a group and their sub-groups.
In the KPI mix tab, an active KPI node is displayed as a checkbox. Only checked KPIs are processed by the KPI mixer. More details about this functionality are described in separate section KPI mix tab.

Tree Context Menu

The KPI tree provides two types of context menus when the user right clicks on the KPI tree node.

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.

KPI Context Menu

Suggest KPI

Suggest KPI opens an email communication where the user can send a new KPI definition suggestion to the support team or any other recipient.

KPI Info

KPI Info displays a pop-up window with basic information about selected KPI (e.g. KPI name, description, unit).

Find correlated KPI(s)

This menu item consists of sub-menu with selected systems or servers in the System tree. The content of this sub-menu depends on whether the selected KPI is defined as a System or Server KPI. It means that when the user selects a System KPI, only selected systems from System tree will be available. Otherwise there will be only available the selected servers.

After the system or server selection, the correlation functionality is executed. This functionality calculates the correlation coefficients 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 coefficients have the values from the interval < -1;1 >. The closer is the coefficient to the value = abs(1) then more correlating KPI is. By default, only first twenty most correlating KPIs which have the coefficient 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).

Set threshold

Set threshold helps the user to create a new alert definition for KPI. When this functionality is selected, a pop-up is displayed in the same screen with predefined values. The user just must set a new threshold value (when predefined 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).

The long description of threshold can be added through the button Long Description and the text is saved when you close the window.

Threshold can be changed also through the context menu.

If the threshold is not set up, the Setup threshold option is displayed in context menu.

If the threshold is setup, the Change threshold option is displayed. Here you can edit existing thresholds or create a new one.

Report Incident

This item just helps users to jump directly into the Incident Management.

Detail tables(s)

When a detail table exists for a selected KPI, the detail table can be displayed as a modal pop-up window. It means that the user can have on the same screen also displayed KPI details data and doesn't have to switch between tabs in the Cockpit.

A detail table can have more versions depending on the system and the time interval which you select. The context menu displays all the versions of detail tables with the relevant systems based to this selection.

When you click on a particular version of a detail table a modal pop-up displays all relevant systems.

When you define the Server name field for a detail table it becomes server dependent. In this case the title "Detail table is server dependent" appears above the table. The server dependent table contains data only of the selected servers.

When you don't select a server by a detail table, then only server independent data is displayed.

Browser not supported