[#PETALSESBCONT-464] The key of incoming TCP-Transporter monitoring metrics is not distinctive enough - Petals Link JIRA

Description:

TCP Transporter metrics : getIncomingConnections and getIncomingMessagesCount return metrics which identify container solely by their IP. This is insufficient, multiple containers can be reachable through different ports on a same IP.

Depends

This issue depends on:
PETALSESBCONT-437 Reimplement the Remote TCP transporter with Apache Netty

This issue blocks:
PETALSESBCONT-465 Incoming TCP Transporter monitoring metrics should return container name instead of container IP address

There aren't workflow transitions executed yet.

Petals ESB Container