(DI-2008) System Tree

In the system tree, a list of systems and their servers are displayed.
In this tree, a node represents a system with a system ID and under this node (system) are its servers with a server name.
By each system, the Alert column displays the alert occurrence.

Tree list of monitored systems without system groups










Tree list of monitored systems without system groups



The systems can be divided into system groups (folders). One system can be placed in multiple groups.

Tree list of monitored systems without system groups 









Tree list of monitored systems with system groups


Each node of the system or server type can be selected. 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 other tabs.
grey-colored node in the tree represents an inactive system. 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 a system and a server has a status icon, which informs us about the current state of the monitoring.
The status icon may have these statuses:


  • - At least one Collector job is executed for the system, which indicates that a background job, which collects KPIs for this Collector job is currently running.
  • - 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 the 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 the previous execution of Collector job was carried out successfully for this system.
  • - System is not reachable through the RFC connection. The reason could be, for example that the system is not responding or the RFC connection is not valid anymore.
  • - System is not monitored because the monitoring of a Collector job didn't start.
  • - The server of a monitored system is excluded from the monitoring; therefore, the accessibility of this server is not checked.
  • - The system/server is not monitored due to an existing restriction in the monitoring, which is setup for a 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.










In the context menu of a group, you can select, or deselect all systems associated with a group, or select all systems below in the group and deselect all other systems. Further you can select only those systems with present alerts, or with alerts, which were occurring for a chosen time period.











 


Context menu for system pool tree