Skip to Main Content
Cloud Management and AIOps


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.

Status Delivered
Workspace Instana
Categories MQ
Created by Guest
Created on May 28, 2025

Mass "insufficient authority" errors in a log for SYSTEM.AUTH.DATA.QUEUE

Dear Colleagues,

due to security policies the customer is not able to grant access to the special queue. Hence they experience the following error in a log:

Error: 2025-05-20T07:10:58.879Z AMQ8077W: Entity 'mqumon01' has insufficient authority to access object SYSTEM.AUTH.DATA.QUEUE [queue]. [CommentInsert1(mqumon01), CommentInsert2(SYSTEM.AUTH.DATA.QUEUE [queue]), CommentInsert3(chg)]

Please consider implementing configuration parameters for the MQ sensor to avoid touching system queues as they're not available anyway.

Thank you

Idea priority Urgent
  • Admin
    Aysha Kanakkovil
    Sep 2, 2025

    Hi All,

    This issue was addressed under CSP case TS019342185.

    Issue:
    Previously, IBM MQ errors were continuously logged when a user without MQM group membership attempted to access SYSTEM.AUTH.DATA.QUEUE, for which they lacked authorization. The customer specifically requested that this system queue not be monitored and that MQM group access not be required.

    Fix:
    To resolve this, we introduced a new configuration parameter: queuesInclude.
    This allows users to explicitly define which queues should be monitored, effectively bypassing unauthorized system queues.

    For example, if a customer has queues named A1, A2, A3, B1, B2, B3, B4, B5, C1, C2, and D1, they can configure:

    queuesInclude: A*, B*, C*, D*
    • A maximum of 10 entries can be specified.

    This enhancement ensures that only intended queues are monitored, thereby avoiding permission issues and unnecessary error logs.

    After confirming with @Kjetil Ommundsen that the fix resolved the issue on the customer end, we are marking this Aha! idea as Delivered.

    Documentation link: https://www.ibm.com/docs/en/instana-observability/1.0.303?topic=technologies-monitoring-mq#configuring

    Thanks!