Hi Satyam,
Assuming that your integration server's name is "TEST_SERVER", and that your application is named "MQTest" and that your message flow is named "callable2", then the following topic strings should work for monitoring and resource stats respectively:
$SYS/Broker/integration_server/Monitoring/TEST_SERVER/MQTest/callable2
$SYS/Broker/integration_server/Statistics/JSON/Resource/TEST_SERVER
Quite a good technique when you begin troubleshooting is often to use wildcards (plus sign "+" for one level and hash sign "#" for multi-level) when subscribing to the topic in order to avoid any spelling mistakes or errors in the topic string.
Another thing worth checking is that the changes you made to your server.conf.yaml file have been applied correctly (eg did you restart your server to have them take effect? Also worth checking the syntax of your yaml file - have you got the correct indentation of spaces ?)
The section of the yaml that you included in your original post is used for turning on message flow monitoring (so is used in relation to the messages published on topic $SYS/Broker/integration_server/Monitoring/TEST_SERVER/MQTest/callable2). There is then a separate part of the flow yaml for turning on Snapshot Flow Statistics but this will be turned on by default (In server.conf.yaml check out Statistics>Snapshot>publicationOn property) ... and then a third area where resource stats is turned on (which relates to the second topic which you mentioned: $SYS/Broker/integration_server/Statistics/JSON/Resource/TEST_SERVER)
If you open a command console session for your running server, you can also check these settings using the following reporting commands:
For monitoring: mqsireportflowmonitoring -i localhost -p 7600 --all-applications --all-flows
For snapshot statistics: mqsireportflowstats -i localhost -p 7600 --snapshot --all-applications --all-flows
If all the above looks good, then next thing to check is that your queue is subscribed correctly.
Cheers,
Ben
------------------------------
Ben Thompson
IBM UK
------------------------------
Original Message:
Sent: Sat September 09, 2023 06:59 AM
From: satyam maurya
Subject: ACE 12 Flow Monitoring events are not reaching to queue
Hi All,
I have 2 issues :-
- I am using ACE 12. I have an independent integration server where i have deployed a message flow, where flow monitoring is enabled at MQinput node. In Debug mode, i can see it is emitting event, which is visible under environment variable. I have enabled flow monitoring in server.conf.yaml file as below
Monitoring:
MessageFlow:
publicationOn: 'active'
eventFormat: 'MonitoringEventV2'
I am subscribing to below topic, as recommended by IBM , but events are not reaching to queue.
Subscribing to event message topics
I have tried with below topic strings :-
$SYS/Broker/integration_server/Monitoring/TEST_SERVER/MQTest/callable2
topicRoot/integration_server/Monitoring/TEST_SERVER/MQTest/callable2
- I have enabled snapshot for collecting the stats but that too is not reaching to queue. I am subscribing to below $SYS/Broker/integration_server/Statistics/JSON/Resource/TEST_SERVER
Please help me on the above.
------------------------------
satyam maurya
------------------------------