Date: Fri, 29 Mar 2024 08:33:46 -0500 (CDT) Message-ID: <1417014532.30296.1711719226585@bmc1-rhel-confprod1.managed.contegix.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30295_922231324.1711719226584" ------=_Part_30295_922231324.1711719226584 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Details Notebook pane displayed below the event list provides all of= the recorded information about an event.
The cards or colu= mns of the details notebook pane organize the information as described in t= he following table:
Event Details Notebook pane
Column name | Sections in subtab | Description of contents |
---|---|---|
Summary | Overview | Hyperlinks to launch Probable Cause Analysis, Sh=
ow Graph(s), and Detailed Diagnostics Basic information about the event, such as status, severity, priority, date= and time of occurrence, object class, object name, host, owner, message, a= nd detailed message |
Event Metric | Event metric information such as metric and its =
value, class, category, monitor category, repeated, and SO For an intelligent event, this field includes additional information such a= s threshold, average value, baseline, baseline type, comparison, duration, = minimum sampling window, absolute deviation, deviation, score, predict, and= auto close |
|
Logs and Notes | Historical Attribu= tes | Historical attributes of the event, such as date=
and time of occurrence, repeated, original severity and priority, origin t=
ime, reported by source, arrived, received, modified, last modifier, time t=
o close, and action count (number of occurrences of actions) A user can enter additional information using the notes text area and click= theNotes icon present in the Logs and Notes table to= view the notes in a larger window. The Logs and Notes table displays notes added by the user, event notificati= on history, event rule history, history of any rule or policy applied, and = event operation history. |
Object | Object Monitored= strong> | Hyperlinks to launch Show Graph(s) and Tools men=
u Information about the monitored object, such as its name, class, owner, and= URL For an intelligent event, this field includes additional information about = groups. |
Host of Object | Information about the host of the monitored obje=
ct, such as its name, address, class, location, and service For an intelligent event, this field includes additional information, such = as VMware host and ID |
|
Parameter | Monitor metric and its value; parameter unit and= its threshold | |
Related Component | Device name, component alias, ID, and type | |
Source | Origin | Information about the origin of the event, inclu= ding class, key, and severity |
Reporter | Information about the adapter or gateway from wh=
ich the event originated, including the tool name, tool ID, monitoring tool=
name, tool suggestion, adapter host, client address, tool class, rule, too=
l key, tool severity, tool address, and tool time (time when the event orig=
inated) By default, this card is not visible. |
|
Internals | Tracking | Tracking information, such as the ID, internal I=
D, account, timeout, collectors, propagations, history, modification histor=
y, Access Control List, and Common Event Model (SEM.) version Alarm ID is displayed in this section if the event selected is of ALARM typ= e. By default, this card is not visible. |
Relationships | Information about events abstracted from this on= e, abstractions, causes and effects, associations, relation source, and eve= nt relations | |
Undefined Attributes | A list of undefined attributes and values | |
Others | dependOnTheSelectedEvent | Information in this card changes according to th=
e type of event selected. The event type is displayed before the slots pres=
ent for that event type, provided the event type has slots that are not pre=
sent in the remaining cards. For example, attributes of a core event that are not displayed in other car= ds, such as ITSM category, company, item, location, manufacturer, model, ve= rsion, and operation category 1, 2, and 3, product name, type, Service Mode= l Component (SMC) impact, and priority might be displayed in this card. |
Apply the necessary filters for the events. For more information abo=
ut applying filters, see Filtering event display for all abnor=
malities.
The Event(s): label on the right side of the event list no=
tebook header displays the number of events for which the filters have been=
applied. The format in which it is displayed is Event(s): <Number o=
f filtered events>. For example, Event(s): 200, where 200 is the to=
tal number of filtered events.
Note
Event count is not displayed for the event list for which the Details No= tebook pane is not present. For example, event count will not display for t= he latest 10 events and maximized event list on Tile and Canvas views. Even= t count is also not displayed if the number of events for a particular filt= er is zero.
Click Close .
If you select more cards than can be displayed, use the tiny right and l= eft arrows to the right and left of the Details Notebook to navigate throug= h the cards.
Click Close.
Note
In the Summary card, when you click Edit Prefer= ences, attributes related to Baseline and Threshold for Intelligen= t events are not available for selection. These attributes cannot be displa= yed in the default Summary card view.
Scroll down to the Logs and Notessection and enter = the annotated text.
Note
Do not include nonprinting characters such as FS (0x1c) and RS (0x1e), a= nd printing characters such as <, >, ', and "in the notes. These char= acters are not supported.