Skip to Main Content
Cloud Management and AIOps
Hide about this portal


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Need the ability to monitor IBM MQ Alias Queues

See this idea on ideas.ibm.com

The customer uses Alias Queues for the IBM MQ applications.   Within Instana, Alias Queues are not monitored.   So, the customer has no visibility into what's happening within their applications.  For example, when they look at the Traces going through MQ, they will see that a message is PUT or GET to/from the queue.  The Queue Name that is called out in the Trace is the Alias Queue.  This causes a couple of problems.   First, it breaks the correlation from the Trace back to the Infrastructure.  The trace indicates "Infrastructure Correlation Missing".   In addition, the customer can't navigate to the Infrastructure and find the Queue because the Alias Queues aren't monitored.

 

This makes it nearly impossible to debug and diagnose their problems.   They see that a transaction is slow or failing, but they have no way to determine what is going wrong within MQ because they don't know which Queue is in use.  They can only see the Alias Queue, but we don't monitor that.  They are forced to log into MQ and find the mapping between the Queues and Alias queues.

Idea priority High