Petals exposes, per container, a JMX API to monitor specific exchanges that goes through the router.
It was mainly used for rate control (not documented) and by Petals WebConsole (not supported anymore).
It relied on the Persistence service (and was its unique user).
It was configured with a configuration file specifying for which interface/service/endpoint the exchanges should be monitored (in practice it seems only the rate control was reading this file and thus only the rate controlled exchanges were monitored... it's not clear).
Rate control is not meant to be a feature of the router itself and could maybe be reimplemented at the CDK level.
Monitoring exchanges as with WebConsole is done with MONIT traces now.
Hence we can remove the RouterMonitor.
Task
Resolved
Major