Expose comprehensive MQIPT operational and performance metrics via JMX so they can be automatically discovered , scraped and validated through instana java agent

We need to expose operation and performance metrics through a standard JMX MBean interface including the following as minimum:

Core runtime Metrics:
Process uptime
Version/build info
Active listeners and their configuration state
Number of active connections per listener
Connections lifecycle events (opening , closing , errorr state..etc)

Traffic & throughput metrics:
Messaging forwarded per second (In case of usage of SSLServer/SSLClient)

Bytes in/out per second

Total messages/bytes forwarded since startup

Average and peak throughput

Network statistics including buffering
TCP errors

Connection health and error metrics:
Connection failures with reason code

TLS handshake failures

Authentication failures

Retry counts

Latency metrics

Resource usage metrics:

Thread pool usage

Memory usage

CPU usage

TCP sockets usage

File descriptors if applicable

Listener specific metric:

Current state

Active sessions

Sessions duration statistics

Route metrics:
listener , destination mapping
Most metrics above but linked to a route /listener within it. (or that could be added to all of them). It's best if we can have a view per route.

Configs exposure like enabled/disabled
forward to destination details

Any specific limits like idletimeout..etc

Best if exposed as com.ibm.mqipt then per type as above i.e. listener , usage , connection , metrics , runtime

Please ensure testing this with instana java agent as it may simply encounter issues for whatever simple reason like metrics data type or how the data is exposed..etc. The whole purpose is to have better visibility hence it's crucial that product team make an actual testing with a monitoring product to simulate , adopt and ensure no further work is needed to make it usable.

If those can be auto discovered by instana , that is great. If there will be struggles then at least it should be doable via the guidance here: JMX Custom Metrics - IBM Documentation and that should be tested.


Documentation:
Please validate performance overhead of enabling JMX and provide documentation on how to enable it 

security like user/password and ensuring this works with instana (we can raise an idea)

should be accessible only via localhost