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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Dead Letter Queue (DLQ) monitoring for currdepth=0 is a very basic and must-have requirement for any tool to be used as MQ monitoring tool. No one would consider Instana as monitoring solution if it lack this very basic functionality. Instana must have ability to configure (in YAML config file) multiple queues names/queue pattern using wild card. Could this be prioritized with an ETA so we can consider switching from Dynatrace to Instana?
Dear colleagues, do we have an ETA for implementing this functionality? This functionality is essential to migrate our CIO MQ infrastructure from Dynatrace to Instana.