Managing events

Events are system alerts that relate to specific performance issues within IBM WebSphere queue managers and their objects. Events are defined in a project, and can apply to multiple connections in that project, and multiple objects under those connections.

This section includes the following topics:

• Configuring events
• Event rule types
• Using the events option (in the Global Actions Bar)
• Event notifications

The purpose of events is to notify middleware administrators of performance variables and problems to help with the monitoring and configuration of managed middleware assets. Events can also indicate overall messaging system issues.
Typically, events are graded or ranked by severity. Depending on the product, informational monitoring may be defined as part of the events structure.

Configuring event rules means setting individual rules types to apply to specific connections associated with the project. Potential events become real, active events when and if defined thresholds are surpassed a specified number of times. At that point, an active event is triggered.

There are also reset events, which are histories of active events for which triggering conditions no longer apply.

More precisely, definitions for the two types of events are as follows:

• Active events report specific connection behaviors that affect the performance of those connections or the system as a whole. Two types of active events exist, or two severity levels: Warning and Critical. Whether an event turns up as Warning or Critical depends on how the Product Administrator configures event severity.

• Reset events occur when the conditions for an active event no longer pertain. The event is cycled to reset status. The purpose is to display event history.

The Events option on the Global Actions Bar contains all active and reset events.