The Codebook tab only appears for a selected notification that represents a root-cause event from an underlying Manager. Such a notification, regardless of its severity, has a value of Yes for its IsRoot attribute. If a notification is notified as a root cause from multiple sources, one Codebook tab is displayed for each source. If the Codebook tab is not displayed but the Fetch Details button is enabled, click Fetch Details to display the tab.
The Codebook tab displays all symptomatic events used in the analysis of a root-cause event. The notification for an active symptomatic event indicates an abnormal condition in an underlying Manager. Notifications for symptomatic events are primarily displayed in this tab and might be displayed in the Notification Log Console. Their display in the console can be configured by your administrator.
In the Codebook tab, information is presented as a tree. Each tree node represents a class associated with a symptomatic event. You can expand the node to display its instance or instances.
The coloring of an active notification for a symptomatic event is determined by its underlying source or whether the event has already been imported into the Global Manager. Typically, the coloring is:
Orange if the symptomatic event is active.
White with black text if the event is inactive.
Gray text if the event is unmonitored or suspended.
In the Codebook tab, if you right-click the background area, a menu with two options appears:
Show Active Only
Click this menu option to display either active and inactive symptomatic event. A check mark appears when only active events are displayed.
Click this menu option to collapse the tree hierarchy. To expand the subtree, select Collapsed again. A check mark appears when the collapsed state is selected.
When the tree hierarchy is collapsed, you can right-click or double-click an instance in the tree to display the Notification Properties dialog box to display additional information.
The instance’s tool tip provides information on the state of the symptomatic event. For example, use a tool tip to determine whether an event is unmonitored or suspended.