Integration


This is an IBM Automation portal for Integration 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 Future consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Nov 19, 2024

RELATED IDEAS

IBM MQ Container and Operator: expose more detailed metrics for prometheus monitoring.

Today, as it is in MQ Operator, mq container expose a set of metrics that seems to be no enought for more detailed monitoring. We will need a plan to monitor our future mq deployment on openshift, and the best tool that suit is for monitoring, is prometheus/grafana.

Im missing metrics regaring messages in/out per queues, queue depth per channel, values withh current specs (so i could get a % of usage of a queue, by example) or utilization of channels.

We could add a parameter in MQ Operator that expose metrics as in here: https://github.com/ibm-messaging/mq-metric-samples

The client collecting metrics could run as a process or a separate container, as part of the deployment or included in mq advanced containers.

Idea priority Medium
  • Guest
    Nov 14, 2025

    We have a large existing MQ estate , which feeds both QM/Infrastructure metrics and queue level metrics into a single Prometheus/Grafana instance.

    The current MQ Container does not expose all of these metrics.  We need both the queue level and the MQ/infrastructure metrics to efficient work through performance issues. . Having only one of these types of metrics only gives part of the story. We also expose these metrics to our MQ user base who expect to see them for the own application analysis.

    The option of using the metrics exposed from the container and also having to run a separate metrics collector (on another pod/externally) to gather queue level makes no sense , adding  complexity to the environment.  It effectively means we must run our own external collector to collect all metrics and not use some of the capabilities that we get as part of the container based QM.

    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.