An instrumentation event is a logical combination of conditions that a queue manager or channel instance detects and puts a special message, called an event message, on an event queue.
IBM® MQ instrumentation events provide information about errors, warnings, and other significant occurrences in a queue manager. You can use these events to monitor the operation of queue managers (with other methods such as Tivoli® NetView® for z/OS® ).
Figure 1 illustrates the concept of instrumentation events.
Event monitoring applications
Applications that use events to monitor queue managers must include the following provisions:
- Set up channels between the queue managers in your network.
- Implement the required data conversions. The normal rules of data conversion apply. For example, if you are monitoring events on a UNIX system queue manager from a z/OS queue manager, ensure that you convert EBCDIC to ASCII.
Event notification through event queues
- Get the message from the queue.
- Process the message to extract the event data.
Conditions that cause events
The following list gives examples of conditions that can cause instrumentation events:
- A threshold limit for the number of messages on a queue is reached.
- A channel instance is started or stopped.
- A queue manager becomes active, or is requested to stop.
- An application tries to open a queue specifying a user ID that is not authorized on IBM MQ for IBM i, Windows, UNIX and Linux® systems.
- Objects are created, deleted, changed, or refreshed.
- An MQSC or PCF command runs successfully.
- A queue manager starts writing to a new log extent.
- Putting a message on the dead-letter queue, if the event conditions are met.