Alignment of IBM MQ Queue Visibility Between Instana Applications and Infrastructure for z/OS Environments

This enhancement is essential to enable true end-to-end observability across IBM Z environments within Instana by ensuring consistent and correlated visibility of MQ queues across both Applications and Infrastructure views.

Currently, MQ queues are:

• Fully visible and monitored in OMEGAMON
• Present in Instana Applications (Flows)
• But incompletely represented or missing in Instana Applications (Flows) -> Queue -> Infrastructure, and often shown as “unmonitored”

This creates a gap where users cannot reliably connect application-level MQ interactions with the actual z/OS infrastructure (LPAR, MQ manager, system). As a result, teams must manually correlate data across tools, which increases complexity and slows down problem determination.

To address this, Instana should provide:

Unified MQ Queue Visibility
All MQ queues observable in OMEGAMON should also be consistently visible in Instana Infrastructure → MQ Queues

End-to-End Correlation
MQ queues displayed in Applications → Flows must be directly linked to their corresponding Infrastructure entities, with navigation showing a fully monitored process instead of “unmonitored”

Environment-Aware Differentiation
In sysplex environments where IUAT and PROD share identical naming (queues, MQ managers, CICS regions), Instana should distinguish resources using:

• LPAR name
• Sysplex/system context
• MQ manager association

Accurate Infrastructure Attribution
Users should be able to clearly identify:

• Which LPAR and MQ manager host a queue
• The associated health, performance metrics, and status

With this capability, Instana would provide a single, consistent observability experience, allowing users to seamlessly navigate from application flows to the underlying infrastructure without ambiguity or data gaps.