To snoop messages on a destination, the snooping function has to be turned ON for that destination. This can be done through Studio as well as programmatically through a Java Application using Admin APIs.
Besides enabling/disabling this function for a destination, the Snooper configuration on a destination can be left set to "Default". If this configuration is not set, global flags decides whether or not snooping is be turned on for a destination. This provides the flexibility of setting the snooping function on all queues and/or topics at the same time.
Following sections provide detailed instructions regarding the Snooper function in FioranoMQ:
- Editing the Snooper Configuration on a Destination
- Viewing Snooped Messages
- Editing the Default (Global) Configuration
- Snooping Related Admin APIs
How it Works
If snooping is turned on, the FioranoMQ Server sends a copy of the incoming messages to pre-configured system topics. An application can then pick up this message and inspect the same.
The System topics used for snooping are:
- SYSTEM_MESSAGE_SNOOPER_TOPIC
- SYSTEM_MESSAGE_SNOOPER_QUEUE
A message on a topic is sent first; messages coming on a queue are sent later.
Security Settings
Security Settings for Snooping are controlled by the ACLs of the above system topics. By default the following restrictions apply:
- Durable subscriptions are not allowed.
- Only the FioranoMQ administrator can "snoop".
- Only FioranoMQ Administrators can edit the ACLs of these topics to modify restrictions. The ACL name is the same as the name of the system topics described above.