Configuring monitoring for message flows
You can configure your message flow to emit event messages that can be used to support transaction monitoring and auditing, and business process monitoring.
Before you begin
- To learn about the basic concepts of monitoring, see Monitoring basics.
- To learn about monitoring IBM App Connect Enterprise event messages, see Configuring and subscribing to performance and monitoring events.
- To decide whether to use monitoring properties or a monitoring profile, see Monitoring properties and monitoring profiles.
- If you are using the default configuration with the built-in MQTT broker, the BusinessEvents group, which includes monitoring events, is disabled for MQTT. Check your pub/sub broker configuration. For more information, see Configuring the built-in MQTT pub/sub broker.
About this task
Note: Monitoring messages are published to IBM MQ pub/sub brokers by using the
persistent as topic option. Publications resolve to be nonpersistent by default,
but you can change a publication to be persistent by configuring named topics in IBM MQ. For more information, see the Subscriptions and message
persistence topic in the IBM MQ product documentation
online.
Monitoring messages are published to MQTT brokers as nonpersistent by default. However, subscribers to MQTT brokers specify the maximum quality of service (QoS) that they require, which determines whether the message is delivered only once or more than once, and whether a confirmation of receipt is required. For more information, see http://mosquitto.org/man/mqtt-7.html.
To receive monitoring events, complete the following tasks.