The navigation tree shows an at-a-glance synopsis of the events and views. Event and component folders are displayed in a hierarchical manner in the navigation tree.
The folders displayed in the navigation tree are divided into the following categories:
Note
Folder and Component views are used as containers for groups, devices, and services. They are access control aware. Folders that contain monitor groups and devices are filtered based on the access control list in the CIs that the monitors and devices are associated with.
To further organize your display, you can add event and component folders, including folders for configuration items (CIs) associated with a service model, beneath these top-level folders, depending on your permissions.
The following table lists the icons for the objects in the navigation tree and provides a description for each object.
Icon | Description |
---|---|
Navigation tree top-level node (Global). The Global node contains the following default collectors:
| |
Navigation tree top-level node (Mine). Based on permissions, users can create event and component folders under this node to organize the event view. | |
Event group collector; an event group subnode of the navigation tree top-level node or another event group node. | |
Child collector node | |
Child group node | |
Child service node |
A CI is any component that needs to be managed in order to deliver an IT service. CIs are under the control of change management. CIs typically include hardware, software, buildings, people, and formal documentation, such as process documentation and SLAs. For more information about CIs, see Service modeling.
Also, you can drag components from one folder that you create to another folder that you create within the navigation tree, and you can drag tiles from the Tile or Canvas view to an existing folder that contains the same type of component; for example, if the tile represents a device, then that tile can be moved to another device folder by using drag and drop.
Users traversing the navigation tree can see and perform actions and operations on only those collectors to which they are granted access, based on different roles in the .mrl file of the collectors.
However, the collector-based permissions on events do not apply when you view an event list from the following locations:
In the navigation tree, the severity icons for a collector dynamically change depending on the severity level of the events for that collector. For example, if there is a Critical event on one of the devices, then the green icon changes to a red icon, indicating a Critical event. This allows you to see the status of devices on your system immediately.
By default, when you open the navigation tree, all nodes and subnodes are loaded even if a node is not expanded. If this causes performance issues, you can change how the navigation tree is loaded. For information, see Improving performance when the navigation tree is loaded in the BMC ProactiveNet Operations Console.