IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Situation event integration with Tivoli Enterprise Console > Default mapping of situation events to IBM Tivoli Enterprise Console events
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Generic mapping for agent specific slots
Generic mapping identifies the target event class based on information out of a situation that is triggered and forwarded to the event server.
The event class name of the IBM Tivoli Enterprise Console event is derived from the attribute group associated with the situation. It is a combination of ITM_ plus the attribute group name associated with the situation. For example, a situation using the NT_Process attribute group will generate a IBM Tivoli Enterprise Console event with class ITM_NT_Process.
Some agents have very long attribute group names, which might cause the generated event class name to exceed the limit imposed by the event server. In these cases, the event class name will be a combination of ITM_ plus the table name of the attribute group.
Additional event slot values are populated with situation attribute values from the situation event data. The slot names are the attribute names after special character processing.
For example, a situation using the Process_CPU attribute causes generation of a slot process_cpu in the IBM Tivoli Enterprise Console event. In case the attribute name conflicts with the slot names in IBM Tivoli Enterprise Console EVENT class or Omegamon_Base class, the applname associated with the attribute group, for example: knt_, is pre-pended to the attribute name to form the slot name.
For complex situations, the situation definition can involve more than one attribute group. In this case, the IBM Tivoli Enterprise Console event class used is derived from the first attribute group encountered in the situation event data of the triggering situation. The exception is when the first attribute group found is Local_Time or Universal_Time; then it is passed over and the next different attribute group, if any, will be used.
For example, if a situation is written for the NT_Process and NT_System attribute groups, NT_Process being the first attribute group, the IBM Tivoli Enterprise Console event class ITM_NT_Process is used. Additional event slots are generated based on the attributes of the attribute group selected.
Special characters for attribute groups and names in IBM Tivoli Enterprise Console events generated from forwarded situation events.
Character: Converts to: <uppercase> (applies only to attribute name) <lowercase> (applies only to attribute name) % percent sign pct_ I/O io R/3 r3 / forward slash _per_ \ backward slash _ (underscore) <space> _ (underscore) ( open parenthesis
) close parenthesis_ (underscore) < open pointed bracket
> close pointed bracket_ (underscore)
After special character processing, the leading and trailing underscore in the final event class or slot name, if any, will be removed.
Parent topic:
Default mapping of situation events to IBM Tivoli Enterprise Console events