Event types

Use this page to view the types of instrumentation event that a queue manager or channel instance can report

IBM MQ instrumentation events have the following types:

• Queue manager events
• Channel and bridge events
• Performance events
• Configuration events
• Command events
• Logger events
• Local events

For each queue manager, each category of event has its own event queue. All events in that category result in an event message being put onto the same queue.

This event queue:	Contains messages from:
SYSTEM.ADMIN.QMGR.EVENT	Queue manager events
SYSTEM.ADMIN.CHANNEL.EVENT	Channel events
SYSTEM.ADMIN.PERFM.EVENT	Performance events
SYSTEM.ADMIN.CONFIG.EVENT	Configuration events
SYSTEM.ADMIN.COMMAND.EVENT	Command events
SYSTEM.ADMIN.LOGGER.EVENT	Logger events
SYSTEM.ADMIN.PUBSUB.EVENT	Gets events related to Publish/Subscribe. Only used with Multicast. For more information see, Multicast application monitoring.

By incorporating instrumentation events into your own system management application, we can monitor the activities across many queue managers, across many different nodes, and for multiple IBM MQ applications. In particular, we can monitor all the nodes in the system from a single node (for those nodes that support IBM MQ events) as shown inFigure 1.

Instrumentation events can be reported through a user-written reporting mechanism to an administration application that can present the events to an operator.

Instrumentation events also enable applications acting as agents for other administration networks, for example Tivoli NetView for z/OS, to monitor reports and create the appropriate alerts.

• Queue manager events
  Queue manager events are related to the use of resources within queue managers. For example, a queue manager event is generated if an application tries to put a message on a queue that does not exist.
• Channel and bridge events
  Channels report these events as a result of conditions detected during their operation. For example, when a channel instance is stopped.
• Performance events
  Performance events are notifications that a resource has reached a threshold condition. For example, a queue depth limit has been reached.
• Configuration events
  Configuration events are generated when a configuration event is requested explicitly, or automatically when an object is created, modified, or deleted.
• Command events
  Command events are reported when an MQSC or PCF command runs successfully.
• Logger events
  Logger events are reported when a queue manager that uses linear logging starts writing log records to a new log extent or, on IBM i, to a new journal receiver. Logger events are not available with IBM MQ for z/OS.
• Event message data summary
  Use this summary to obtain information about the event data that each type of event message can contain.

Parent topic: Instrumentation events