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.

Add a new idea Subscribe
Status Under review
Workspace Instana
Categories MQ
Created by Guest
Created on May 15, 2025

RELATED IDEAS

Local binding mode support for Local monitoring for MQ deployed in OCP cluster

At the moment Instana agent only supports client binding mode for locally monitored OpenShift deployed MQ.
https://www.ibm.com/docs/en/instana-observability/current?topic=technologies-monitoring-mq#common-scenarios

This required agent configuration to be added / amended for every new QM deployed into a cluster. This would be painful to manage going forward.

Is there a way we can avoid this config at each QM level and just specify at a top level, the same keystore / channel / cipher to attempt to connect to any QM deployed in the cluster?

We tried to add these attributes directly under the com.instana.plugin.ibmmq level, but it didn’t appear to do anything.

Idea priority High
  • Guest
    May 16, 2025

    Most of the QMs deployed in our organisation are standardised via a pattern. Thus, every QM would have the same configuration applied to allow Instana to connect/monitor the QMs. We don't want application teams who manage their own QM instances to have to know anything about the monitoring stack in order for their QMs to be monitored, so having the ability to have a generic set of configuration params to use to attempt connection to every QM (auto-discovered) in a cluster rather than individual config per QM in the agent configuration_yaml would be a big help.

    Also, we use gitops to manage K8s YAML configuration in the Openshift clusters, so having to put this configuration for every QM deployment is painful, and also is subject to change management processes etc.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.