Resolution:
Description:
= = = = = = =
How monitoring messages differ from standard messages?

Environment:
= = = = = = =
ALL

Resolution:
= = = = = =
An application can receive and display all or part of a
monitor message, just as it would handle any message sent
to a topic. However, there are some ways in which monitor
messages are handled differently from standard messages:

- Monitor messages cannot be routed to other servers.
- Monitor messages are not stored persistently on disk.
- Monitor messages are not swapped from process memory to disk.
- Monitor messages cannot be bridged to other destinations.
- Topics starting with $sys.monitor do not participate in any
  permission inheritance from parent topics other than those
  starting with $sys.monitor (that is, *.* or *.> is not a parent
  of $sys.monitor).
- So granting permission to a user to subscribe to > does not
  allow that user to  subscribe to $sys.monitor topics. You must
  explicitly grant users permission to $sys.monitor topics
  (or parent topics, such as $sys.monitor.admin.*) for a user
  to be able to subscribe to that topic.

We can have any number of applications that subscribe to monitor
messages and  can create  different applications that subscribe
to different monitor topics, or we can create one application
that subscribes to all desired monitor topics.  The  topic
subscribers can also use message selectors to filter the monitor
messages so your application receives only the messages it is
interested in.

Reference:
= = = = = =
For information, please refer Chapter 16 Monitoring Server Activity : Monitoring Server Events
In EMS user manual.

Keywords/Tags:
= = = = = = = = =
Monitoring messages.