As AppDynamics user I need JMX MBeans to contain a consistent set of expected metrics for a given type

When using JMX instrumentation wildcards in AppDynamics, various MQ objects of the same type, example SENDER or SVRCONN channels return different metric parameters even though they are the same type. This means the JMX MBean does not contain a consistent set of expected metrics and this causes AppD to assume the expected metric is NULL.

After two attempts getting a NULL response to the metric value, AppD disables the metric and it becomes unusable.

This is only an issue when using a * wildcard to collect the MBean metrics. 

This is similar to the ZOS issue. 

The fix would be to create different Types for each channel or ZOS channel initiator or to add dummy metrics to pad out the missing metrics.