EVENT is the root class for all BMC Impact Manager event classes. Its class definition is internal and is not visible in the Knowledge Base. This internal class is defined in mc_root_internal.baroc file, and extended in the mc_root_redef.baroc file
It is possible, but not recommended, to redefine the EVENT class in a Knowledge Base. Redefining the base EVENT class results in the merging of the internal definition with the redefined definition in the Knowledge Base. The following table lists the internal event slot definitions alphabetically, together with an explanation for each slot.
Table 2-3 EVENT Class Slot Definitions (Part 1 of 7)
Slot Definition Description
adapter_host STRING The name of the machine on which the adapter that sent the message resides.
administrator STRING Name of the entity that last modified the event, as user@host or package:rulename.
date STRING If empty when entering the cell, it is set as the textual format of
date_reception, as defined with the parameter DateFormat.
date_reception INTEGER,
representation = date
Time stamp that is set by the adapter or gateway that sends the event. If not set by the source, on its arrival at a cell, its value is set to the value of incident_time. If there is no incident_time value, its value is set to the mc_arrival_time value.
duration INTEGER,
parse = no;
Elapsed time, in seconds, between the date_reception time and the time at which the event was closed.
event_handle INTEGER,
parse = no, read_only = yes
hostname STRING Name of source machine, as a fully qualified domain name, if available. This slot is deprecated and may be removed in the future.
mc_abstracted LIST_OF INTEGER, parse = no;
System reserved.
mc_abstraction LIST_OF INTEGER, parse = no;
System reserved.
mc_acl LIST OF STRING,
parse = no;
A list of the additional roles that can access the event. Role ownership for the event is determined by adding roles defined in this slot to those roles defined on a collector that contains the event. Event-level, role-based access is implemented in BMC Impact Explorer.
mc_action_count INTEGER Counter contains the number of programs run for this event.
mc_arrival_time INTEGER,
representation = date;
Time stamp at which the event arrived at the BMC Impact Manager network at either an adapter or a cell. Its value is never zero (0).
mc_associations LIST_OF STRING; parse = no;
System reserved.
mc_bad_slot_names LIST_OF STRING Names of slots with a parsing error.
mc_bad_slot_values LIST_OF STRING Corresponding values of slots with a parsing error.
mc_cause INTEGER,
parse = no;
System reserved.
mc_collectors LIST_OF STRING; parse = no;
System reserved.
mc_client_adddress STRING, parse = no;
The effective IP address of the client that sent the event. This slot replaces the former mc_origin slot.
mc_date_ modification
INTEGER,
representation = date;
Time stamp of last modification of certain slots. The slots are those mentioned in mcell.modify. Table 2-3 EVENT Class Slot Definitions (Part 2 of 7)
mc_effects LIST_OF INTEGER, parse = no;
System reserved.
mc_history LIST_OF STRING; System reserved.
mc_host STRING; Fully-qualified name of the host on which the problem occurred.
mc_host_address STRING; Typically, the network address corresponding to mc_host. Technically, this slot can contain some other type of information in situations in which a host value is not meaningful.
mc_host_class STRING; A type of host. This field is important to implementing generic actions, such as rebooting a machine on which a problem has occurred. In the background, a generic action can be translated into a specific action based on this field.
mc_incident_time INTEGER,
representation = date;
Time stamp corresponding to the time at which the incident causing the event occurred. Its value is zero (0) if the time unknown. This time stamp can be set by an adapter or a gateway.
mc_it_mgt_process STRING; ITIL process that is influenced by this event. Possible examples are: AVAILABILITY, SECURITY, CHANGE, PERFORMANCE, INCIDENT, SLM, CHANGE. mc_local_reception_ time INTEGER, representation = date;
Time stamp when the event arrived in the local component. It is never zero (0).
mc_location STRING; Location at which the managed object resides.
mc_modhist LIST_OF STRING; System reserved. Table 2-3 EVENT Class Slot Definitions (Part 3 of 7)
mc_notes LIST_OF STRING; A list of free text annotations added to the event. The contents of this slot is implementation-dependent. Rules or users should not rely on a particular value in this slot. To use this slot’s contents, you must use the appropriate access functions.
mc_object STRING; String that identifies the
subcomponent that caused the event on the host. If this value cannot be derived from the original event, it should be acquired as part of event enrichment, possibly during the Refine event-processing phase.
mc_object_class STRING; String that identifies the class to which mc_object belongs.
mc_origin STRING; Event-management system that is
as close as possible to the event source. For example, PATROL agent -> BMC II for PATROL ->BMC EM. The mc_origin value would be the PATROL agent name. The mc_tool value would be string composing the PATROL agent name and its port. This slot has been redefined. The former mc_origin slot is renamed to be mc_client_address slot.
mc_origin_class STRING; Identifier that indicates the type of event-management system that originally issued the event. This slot may have the same value as the mc_tool_class slot.
mc_origin_key STRING; Unique key with which the originating event-management system enumerated the event. In a two-tiered, event-management system, this might as the same value as the mc_tool_key slot.
mc_origin_sev STRING; Severity value given by the mc_origin.
In a two-tiered, event-management system, this might as the same value as the mc_tool_sev slot.
mc_parameter STRING; Name of the parameter that by going into alarm or by triggering a state change caused the event.
mc_parameter_value STRING; The actual value of the parameter that caused the event.
mc_propagations LIST_OF STRING, parse = no;
System reserved.
mc_smc_causes LIST_OF STRING, parse = no;
System reserved.
mc_smc_effects LIST_OF STRING, parse = no;
System reserved.
mc_smc_id STRING System reserved.
mc_smc_impact INTEGER, Default = 0;
System reserved.
mc_smc_type STRING; System reserved.
mc_tool STRING; Any value that can more closely
identify the event provider (tool) within the specified
mc_tool_class. A primary use of the field is to provide the information necessary to enable an external action to initiate communication with the event provider.
For example, If the mc_tool_class is PATROL, the mc_tool value should be a string composing the PATROL agent name and its port value so that an external action can trigger communication with it. Table 2-3 EVENT Class Slot Definitions (Part 5 of 7)
mc_tool_class STRING; An identifier that indicates type of event provider (tool) that reported the event to the cell. Typically, each type of adapter has a specific mc_tool_class value; for example, SNMP. T
The identifying value, itself, is not important, but different tools should not use the same identifier. The cell does not enforce this constraint.
mc_tool_key STRING; Unique key with which the sending tool enumerated the event.
mc_tool_sev STRING; Severity value from the mc_tool. This value does not have to be the same as the severity assigned by BMC Impact Manager. For example, To the IT staff, a failed router is a critical alert. But, if there is a back-up router, the event is not critical from a service viewpoint.
mc_ueid STRING,
read_only = yes;
Universal event identifier.
msg STRING Text that describes the incident.
origin STRING IP address of source machine.
This slot is deprecated and may be removed in the future.
repeat_count INTEGER Number of times that the same event has been received.
severity SEVERITY,
default = WARNING
Severity of the event.
source STRING Name of the source entity where the
event occurred.
This slot is deprecated and may be removed in the future.
status STATUS,
default=OPEN;
Status of the event. Table 2-3 EVENT Class Slot Definitions (Part 6 of 7)
sub_origin STRING Address of source component. This slot is deprecated and may be removed in the future.
sub_source STRING Component of the source.
This slot is deprecated and may be removed in the future.