CORE_EVENT is the base class for all cell event classes. Its class definition is internal and is not visible in the Knowledge Base. This class cannot be changed and is documented in the mc_root_internal.baroc file.
All cell components populate these slots as specified. Internal cell-generated events are also populated as specified.
CORE_EVENT base class slots
Slot | Type | Description |
---|---|---|
| STRING | Name of the host where the adapter that sent the event is running |
| STRING | Identification of the user that last modified the event, as |
| STRING | If empty, when entering the cell, it is set as textual format of |
| INTEGER | Timestamp as set by the source of the event |
| INTEGER | Elapsed time, in seconds, from event creation to the time the event was closed |
| INTEGER | Event identifier in the local cell |
itsm_category | STRING | Category of the related CI from BMC Atrium CMDB for the specified event |
itsm_company | STRING | Company of the related CI for the specified event |
itsm_incident_id | STRING | Incident id of the related Incident for the specified event |
itsm_incident_status | STRING | Incident status of the related Incident for the specified event |
itsm_item | STRING | Item attribute of the related CI from BMC Atrium CMDB for the specified event |
itsm_location | STRING | Location of the related CI for the specified event |
itsm_manufacturer | STRING | Manufacturer information of the related CI from BMC Atrium CMDB for the specified event |
itsm_model_version | STRING | Model version of the related CI from BMC Atrium CMDB for the specified event |
itsm_operational_category1 | STRING | Operational Categorization 1 Value for the specified event. Same gets populated into Op cat 1 for the incident |
itsm_operational_category2 | STRING | Operational Categorization 2 Value for the specified event. Same gets populated into Op cat 2 for the incident |
itsm_operational_category3 | STRING | Operational Categorization 3 Value for the specified event. Same gets populated into Op cat 3 for the incident |
itsm_product_name | STRING | Product name of the related CI from BMC Atrium CMDB for the specified event |
itsm_type | STRING | Type of the related CI from BMC Atrium CMDB for the specified event |
| LIST_OF INTEGER | System reserved |
| LIST_OF INTEGER | System reserved |
| STRING | Identifies the account associated with the event |
| LIST OF STRING | Controls |
| INTEGER | Number of actions performed on the event |
| INTEGER | Timestamp when the event arrived at the network at either an adapter or a cell |
| LIST_OF STRING | System reserved |
| LIST_OF STRING | List with names of slots that could not be set when the event was reserved |
| LIST_OF STRING | Corresponding values of the bad slots |
| INTEGER | System reserved |
| STRING | Network address of the host where the adapter that sent the event is running |
| LIST_OF STRING | System reserved |
| INTEGER | Timestamp of last modification of certain slots |
| LIST_OF INTEGER | System reserved |
| MC_EVENT_CATEGORY | High-level normalized category of the object the event represents based on an appropriate Information Technology Infrastructure Library (ITIL) core process. Possible categories are as follows:
|
| STRING | Denotes the version of the event model that instantiates the event. The event model version is in the format major_version.minor_version.service_version required for compatibility purposes. |
| LIST_OF STRING | A list of tuples is as follows:
|
| MC_EVENT_SUBCATEGORY | Subcategory of the object the event represents based on an appropriate Information Technology Infrastructure Library (ITIL) core process. Possible values are as follows:
|
| LIST_OF STRING | System reserved |
| STRING | Fully qualified name of the host on which the problem occurred |
| STRING | Network address corresponding to the Note This slot can contain some other type of information in situations in which a host value is not meaningful. |
| STRING | Type of host |
mc_host_id | INTEGER | If the event is associated to a BMC_ComputerSystem CI, this slot contains the DeviceID of that CI. |
| INTEGER | Date and time when the event was reported (represented as a timestamp) |
| INTEGER | Timestamp corresponding to the time at which the incident causing the event occurred |
| INTEGER | Timestamp when the event arrived in the local component |
| STRING | Location at which the managed object resides |
| STRING | Expands the information in |
| LIST_OF STRING | System reserved. Contains the history during propagation of an event modification from one Cell to following Cells. Used to detect modification propagation loops. |
| LIST_OF STRING | List of free text annotations added to the event The |
| LIST_OF STRING | Indicates the status of the event with respect to the notification system over time |
| STRING | Sub-component of the host to which the event is related |
| STRING | Identifies the class of an object |
| STRING | Identifies the owner of the source component |
| STRING | Address used to cross-launch directly to the component |
| LIST_OF STRING | Slot containing a list of operation history entries |
| STRING | Event management system that is closest to the source of the event as possible |
| STRING | Identifies the event management system type |
| STRING | Unique key that the originating tool used to enumerate the event |
| STRING | Severity as given by the |
| MC_PRIORITY | Records the original priority of the event upon insertion to the cell, which is needed to determine whether an event has been escalated or de-escalated |
| STRING | Severity of the event defined by the event monitor component |
| SEVERITY | Records the original severity of the event to determine whether the event's severity has been modified |
| STRING | Current user assigned to the event |
| STRING | Name of the metric or property that went into alarm or that triggered the event |
| STRING | Threshold value that was crossed to cause the generation of the event |
| STRING | Unit description of the metric |
| STRING | Actual value of the parameter |
| MC_PRIORITY | Current priority of the event. Following are the possible values:
|
| LIST_OF STRING | System reserved |
mc_relationships | STRING parse = no | System reserved |
| STRING | The |
| STRING | Service related to the event |
| STRING | Event is attached to the service impact management component with the specified identifier |
| MC_SMC_IMPACT | Indicates whether an event is elected, attached, or has an impact on a service impact management component
|
| REAL | Prioritizes events with respect to their impact on the service model
|
| STRING | Value is set to the class of the service impact management component to which the event is attached |
| INTEGER | Event timeout in seconds |
| STRING | For BMC Event Management events, |
| STRING | The network address of the Reporter |
| STRING | For BMC Event Management, |
mc_tool_id | STRING | Identifier of the tool reporting an event |
| STRING | Unique key used by the sending tool to enumerate the event |
| STRING | Name of the adapter or integration mapping rule that generated the event |
| STRING | Severity as given by |
| STRING | The Reporter's suggested solution to the problem posed by the event. This is similar to expert advice information that other applications provide. |
| INTEGER | Date and time (as a timestamp) when the event report was created. The ReportTime value must be read as using the time scale Coordinated Universal Time (UTC) unless a particular time zone or the value Z (Zulu time for UTC) is otherwise specified. |
| STRING | The address used to cross-launch directly to the Reporter |
| STRING | Universal event identifier When an event is propagated, the receiving cell gets a new local identifier, |
mc_using_organization | STRING | This slot is used to populate Company name. This is used in tenant filter |
mc_using_organization_id | STRING | This slot is used to populate Company id. This is used in tenant filter |
| STRING | Text description of the event |
pn_detail_diag | INTEGERhidden=yes | System reserved |
pn_detail_diag_count | INTEGERhidden=yes | System reserved |
pn_device_name | STRING | This slot contains the Component name |
| INTEGER | Number of copies received from this event |
| SEVERITY | Severity value of the event. Possible values are as follows:
|
| STATUS | Status value of the event. Possible values are as follows:
|
2 Comments
Arif Alibay
Our customer found some missing statements while working with this BPPM 9.6-online-documentation
https://docs.bmc.com/docs/display/public/proactivenet96/CORE_EVENT+base+event+class
-->mc_event_model_version Type should be STRING, default = '1.1.00';
-->slot "mc_tool_time" , the Type should be "Integer ,representation = date"
-->slot "mc_tool_time" , the Type should be "Integer ,representation = date"
-->slot "mc_yesno" is *not* a slot but an enumation, we should either remove it from the slot column or change the name of the column as Slot/enumeration ...
-->slot "mc_tool_id" is missing.
Thanks,
Arif
Pete Flores
A customer opened an issue asking about the mc_relationships slot. He tried checking here but it's not documented even though it's in the mc_root_internal.baroc. Can we add it?
Thanks,
Pete