You can subscribe to topics that return messages about the configuration, state, or operational status of your integration node, integration server, or message flows.
A subscriber can send a subscription request to the pub/sub broker that specifies the event messages that the subscriber wants to receive. To receive IBM® Integration Bus event messages, use the following information to define the subscription requests.
IBM/IntegrationBus/integrationNodeName/Status/ExecutionGroup/integrationServerName
$SYS/Broker/integrationNodeName/Status/ExecutionGroup/integrationServerName
topicRoot/+/StatisticsAccounting/#
where topicRoot is IBM/IntegrationBus for
an MQTT pub/sub broker and $SYS/Broker for an MQ
pub/sub broker. For more information about how you can use wildcards,
see Special characters in topics.You can subscribe to IBM Integration Bus messages in the following categories:
topicRoot/integrationNodeName/Statistics/JSON/recordType/integrationServerName/messageFlowName
topicRoot/integrationNodeName/StatisticsAccounting/recordType/integrationServerName/messageFlowName
mqsichangeproperties IBNODE -b pubsub -o OperationalEvents/MQ -n format -v none
The
pubsub component change overrides the use of environment variables.
For more information, see Parameter values for the pubsub component.topicRoot/integrationNodeName/Statistics/JSON/Resource/integrationServerName
topicRoot/integrationNodeName/ResourceStatistics/integrationServerName
For more information about how to interpret the resource statistics that are included in the publication, see Viewing resource statistics data in the web user interface.
topicRoot/integrationNodeName/Configuration/ExecutionGroup/integrationServerName
For an example message, see Example: changes to the local configuration of the integration node.
topicRoot/integrationNodeName/integrationNodeName/Status
topicRoot/integrationNodeName/Status/ExecutionGroup/integrationServerName
For an example message, see Example: changes to state of an integration node or message flow.
The message rate statistics are collected at a checkpoint that occurs every 20 seconds. The total message rate is calculated at this checkpoint, and if the total message rate exceeds the notification threshold, the out of range XML message is published. If the total message rate continues to stay above the notification threshold, then no further out of range messages are published.
topicRoot/integrationNodeName/WorkloadManagement/AboveThreshold/integrationServerName/applicationName/libraryName/messageFlowName
topicRoot/integrationNodeName/WorkloadManagement/AboveThreshold/integrationServerName/libraryName/messageFlowName
topicRoot/integrationNodeName/WorkloadManagement/AboveThreshold/integrationServerName/applicationName/messageFlowName
topicRoot/integrationNodeName/WorkloadManagement/AboveThreshold/integrationServerName/messageFlowName
topicRoot/Monitoring/integrationServerName/messageFlowName
Subscribers receive statistics reports only from those integration nodes that are enabled to produce statistics.