4.2.2 Event acquisition filter

The event acquisition filter is used by (the event base service of) JP1/IM - Manager to filter JP1 events acquired from JP1/Base. You can set multiple conditions in the manager before using this filter and then switch and use one of the conditions.

For the event acquisition filter, define the conditions of JP1 events that need to be monitored by JP1/IM - Manager. Generally, the JP1 events indicating that severe events were generated within the monitoring system are the JP1 events that need to be monitored by JP1/IM - Manager. After the JP1 events pass through the event acquisition filter, they become the following JP1 events:

• JP1 events monitored on the Monitor Events page or Severe Events page of the Event Console window

• JP1 events that trigger automated actions

• JP1 events that change the status of a monitoring object

• JP1 events that issue a correlation event (correlation source events)

For example, if the manager of JP1/IM and a product that issues a large number of normal events are running on the same machine (such as when JP1/AJS issues events for successful execution of jobs), JP1 events required for system monitoring might be buried in those events. In such case, you can use the event acquisition filter to acquire only the JP1 events to be monitored, so that system monitoring will not be adversely affected.

Event acquisition filters reside in JP1/IM - Manager and can be set from JP1/IM - View. They affect all JP1/IM functions, including JP1 event monitoring, automated actions, and object status monitoring.

If the LANG environment variable set for JP1/IM - Manager and the LANG environment variable set for the JP1/Base event server are different, the event acquisition filter does not operate normally.

If the integrated monitoring database is used, JP1 events that pass through the event acquisition filter are saved.

Note

• To display events in JP1/SES format in JP1/IM - View, you must change the event acquisition filter settings to acquire JP1/SES events. The default settings do not display JP1/SES events.

• If you are not using the integrated monitoring database, the event acquisition filter also applies to the event generation service.

  The event generation service is inactive by default. When it is started, however, the filter definitions in effect for the event base service are also applied to the event generation service.

  If you are using the event acquisition filter (for compatibility), the event generation service operates without any filter conditions.

  For details about the event generation service, see 4.3 Issue of correlation events.

• Mapping of the event source hosts is available for JP1 events acquired from the event service. Therefore, for event acquisition filter conditions used when JP1 events are acquired, you cannot specify the event source hosts.

Setting multiple event acquisition filters

You can set multiple event acquisition filters.

For example, if you want to change the type of JP1 events collected or the host from which they are acquired according to the time of day (business hours or night time), you can set different event acquisition filters for the different times of day and switch between them.

Events issued when an event acquisition filter is switched

When you switch to a different event acquisition filter, JP1/IM - Manager issues JP1 events (event IDs 00003F13 and 00003F20) reporting the changed filter conditions. The messages give the name of the filter now in effect and the arrival time and serial number of the last event received by JP1/IM - Manager before the filter was switched.

These JP1 events (event IDs 00003F13 and 00003F20) report that the new event acquisition filter came into effect from the first event received by JP1/IM - Manager after the event corresponding to the arrival time and serial number given in the messages. That is, the filter change and JP1 event issue do not occur at the same time.

For example, if a large number of other JP1 events were issued at the time the filter was switched, there might be a delay before the JP1 events (event IDs 00003F13 and 00003F20) reporting the changed filter conditions appear in the Event Console window. This could mean that the first JP1 event acquired with the new filter appears before the JP1 events reporting the filter change.

To identify the first JP1 event acquired with the new event acquisition filter, check the messages (event IDs 00003F13 and 00003F20) to find the last JP1 event acquired before the change. (Subsequent JP1 events will have been acquired with the new event acquisition filter.)

For details about the JP1 events (event IDs 00003F13 and 00003F20), see Chapter 3. JP1 Events in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference. Note that these JP1 events are not issued when the event acquisition filter is operating in compatibility mode.

To Page Top