Each Experience Manager Monitor can forward events to non-Operations Center subscribers in XML or IBM* Tivoli* Enterprise Console T/EC format. To implement this, edit the settings in the /OperationsCenter_ExperienceManager_install_path/config/monitor.properties file.
Store events or forward them to non-Operations Center subscribers in XML or T/EC format. Filter event information based on column name.
The following code shows a forwarded T/EC event:
### EVENT ### ICMP; eventID="-694373732"; createDate="2004-09-13 13:09:57.415"; alarmSeverity="OK"; responseTime="4"; description="Success: Response Time = 4ms"; eventType="synIcmpAlarm"; appName="test1"; hostName="boilermakers.mosol.com"; hostPort="6789"; scenarioName="002-ping"; icmpSynHost="www.yahoo.com"; icmpSynMaxCount="5"; END ### END EVENT ###
The following code shows a forwarded XML event:
<event eventID="-1069746093" createDate="2004-09-13 13:10:59.054" alarmSeverity="OK" responseTime="28" description="Success: Response Time = 28ms" eventClass="TRACERT" eventType="synTracertAlarm" appName="test1" hostName="boilermakers.mosol.com" hostPort="6789" scenarioName="003-tr" tracertSynHost="www.yahoo.com" tracertSynMaxCount="30" />
To set up event storage or forwarding:
Modify the /OperationsCenter_ExperienceManager_install_path/config/monitor.properties file. Table 4-2 describes the various event forwarding properties and the valid values.
Table 4-2 Event Forwarding Properties
Property |
Description |
---|---|
Event.forwarding.output |
If True, forward events using Event.forwarding.format, in addition to the Experience Manager events sent to the Operations Center server. Specify True or False. |
Event.forwarding.format |
The format used for storage or transmission. Specify XML or TEC. |
Event.forwarding.type |
Specifies whether the monitor stores or sends the event. Set it to TRANSMIT or STORE. |
Event.forwarding.outputfile |
If Event.forwarding.type equals STORE, specify the file format for storing events: TEC or XML. For example, d:/OperationsCenter_ExperienceManager_install_path/events/tec_file.txt. |
Event.forwarding.host |
If Event.forwarding.type equals TRANSMIT, specify the hostname to which the events are transmitted. |
Event.forwarding.port |
If Event.forwarding.type equals TRANSMIT, specify the port number on the host to use for transmission. |
Event.forwarding.filterout |
Event-specific data used to filter the event before forwarding. Use a semicolon to delimit values when specifying more than one filter. Refer to the Experience Manager Hierarchy file in the /OperationsCenter_install_path/database/examples directory for filter examples. The following core fields cannot be filtered: eventide, createDate, alarmSeverity, responseTime, description, eventType, appName, hostname, and hostPort. For example, to filter out the HTTP code and bytes from all HTTP tests: Event.forwarding.filterout=httpSynCode;httpSynBytes |
When the Experience Manager Monitor directly forwards events to IBM Tivoli Enterprise Console (T/EC) servers, carriage returns (<CR>) and tab characters appear after the $ character. This can cause the T/EC reception plug‑in for IBM Micromuse* Netcool*/OMNIBUS to improperly map alarm properties to their alarms. The default hard-coded header and footer sequences match the following:
Event.forwarding.TEC.header=\\n### EVENT ###\\n Event.forwarding.TEC.footer=END\\n### END EVENT ###\\n
To correct this, modify the following properties in the /OperationsCenter_ExperienceManager_install_path/config/monitor.properties file. Configure both properties with embedded line feed (0x0A) characters using the sequence \\n.
Event.forwarding.TEC.header: Specifies the header data sent at the beginning of a TEC event.
Event.forwarding.TEC.footer: Specifies footer data sent at the end of a TEC event.