Monitor Messages : Description of Monitor Topics

Description of Monitor Topics
Table 75 describes each monitor topic.
Table 75 Monitor topics
Stored messages fall below a destination’s limit, disengaging the flow control feature.
The message published contains low-level PGM statistics from the server and multicast daemons.
A message consumer subscribes or attempts to subscribe to a multicast-enabled topic.
$sys.monitor.D.E.destination
A message is handled by a destination. The name of this monitor topic includes two qualifiers (D and E) and the name of the destination you wish to monitor.
D signifies the type of destination and whether to include the entire message:
T — topic, include full message (as a byte array) into each event
t — topic, do not include full message into each event
Q — queue, include full message (as a byte array) into each event
q — queue, do not include full message into each event
E signifies the type of event:
r for receive
s for send
a for acknowledge
p for premature exit of message
* for all event types
For example, $sys.monitor.T.r.corp.News is the topic for monitoring any received messages to the topic named corp.News. The message body of any received messages is included in monitor messages on this topic. The topic $sys.monitor.q.*.corp.* monitors all message events (send, receive, acknowledge) for all queues matching the name corp.*. The message body is not included in this topic’s messages.
The messages sent to this type of monitor topic include a description of the event, information about where the message came from (a producer, route, external system, and so on), and optionally the message body, depending upon the value of D.
See Monitoring Messages for more information about message monitoring.