Chapter 2. Enhancements

ENTMQIC-2146 - Enhanced INFO logging in the router
Logging at the INFO level has been enhanced. You can now track the lifecycle of each router’s connections and links.
When a connection is opened, a log entry is created providing you with the following information:
- Unique ID of the connection
- Direction of establishment (in or out)
- Host and port of the remote end of the connection
- Virtual host in use (if the connection is multi-tenant)
- Type of encryption being used
- Type of authentication mechanism being used
- User name for the connection
- Container ID of the peer AMQP container
- Any connection properties supplied by the peer
In addition, you can now trace links by using INFO logs. When a link is attached (that is, created), a log entry is created providing you with the following information:
- Unique ID of the link
- Direction of message flow - in for messages flowing into the router (from a sender on the endpoint) and out for messages flowing out of the router (to a receiver on the endpoint)
- The link’s terminus addresses (source and target)
When a link is detached, a log entry is created providing you with the link’s terminal statistics, and any error conditions related to the termination of the link.

ENTMQIC-2147 - Enhanced metrics available from the router
AMQ Interconnect now provides several new AMQP link statistics that help you to identify delayed message deliveries and troubleshoot slow consumers.
For each link, the router now reports the following new statistics:
- Global number of delayed settlements
- Rate of delivery settlement
- Indication of "slow status" (a link is identified as "slow" if it has a backlog of undelivered or unsettled deliveries and a low rate of settlement)
You can view these new per-link router statistics by using the qdstat tool, the web console, or viewing the router’s logs.

ENTMQIC-2170 - Optionally enforce access policy on connections established by the router
When the router opens a connection to an external AMQP container, you can now define policies that restrict the resources that the external container can access on the router. Previously, policies could only be applied to inbound connections. This meant that it was possible for external containers to open links to any address on the router (such as $management, for example).
To define the resources that an external container can access over a connection, you must create a connector policy. For more information, see this example of a connector policy.