IBM GC34-5557-00 Instrumentation Events, Types of Event, Queue manager events, Performance events

Instrumentation Events

Instrumentation Events

You can use MQSeries instrumentation events to monitor the operation of queue managers.

Instrumentation events cause special messages, which are called event messages, to be generated whenever the queue manager detects a predefined set of conditions. For example, the following conditions give rise to a Queue Full event:

vQueue Full events are enabled for a specified queue, and

vAn application issues an MQPUT call to put a message on that queue, but the call fails because the queue is full.

Other conditions that can give rise to instrumentation events include:

vA predefined limit for the number of messages on a queue being reached

vA queue not being serviced within a specified time

vA channel instance being started or stopped

If you define your event queues as remote queues, you can put all the event queues on a single queue manager (for those nodes that support instrumentation events). You can then use the events that are generated to monitor a network of queue managers from a single node.

Types of Event

MQSeries events are categorized as follows:

Queue manager events

These events are related to the definitions of resources within queue managers. For example, if an application attempts to open a queue but the associated user ID is not authorized to perform that operation, a queue manager event is generated.

Performance events

These events are notifications that a resource has reached a threshold condition. For example, a queue has reached its queue-depth limit following an MQGET request, or a queue has not been serviced within a predefined period of time.

Channel events

These events are reported by channels as a result of conditions they detect during their operation. For example, a channel event is generated when a channel instance is stopped.

Chapter 1. About MQSeries 7