Skip to Main Content
Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Not under consideration
Created by Guest
Created on Jun 22, 2022

Make Listener Port and Activation Spec status available as prometheus GAUGE metric

As a WAS admin using prometheus for JVM monitoring, I'd like an exposed GAUGE metric that tells me what the status of a ListenerPort or Activation Spec would be on a JVM or Application. 0 could represent stopped and 1 could represent running. It could look something like this: was_messagedrivenbean_listenerport{name="myListenerPort",cell="linuxServerCell01",node="linuxServerNode01",server="My_App_JVM"} 0 And since ActivationSpecs are the newest iteration of the MDB Listener, those could look something like this : was_messagedrivenbean_activationspec{appname="MyApp#MyListener.jar","endpoint="MDB_J2CMessageEndpoint","activationSpec="myActivationSpec",cell="linuxServerCell01",node="linuxServerNode01",server="My_App_JVM"} 1 Being able to show the MDB status on a dashboard or even better, to configure alertmanager to show when a listener goes into a stopped state would be incredible helpful.

Also, including the "initial state" as part of the listener port status as part of the eval would be helpful so that in case we have an LP that has a initial state of stopped, the status could be considered 1 or OK since we would want the LP down on purpose and don't want to consider it "down". It's only when a listener port is stopped and the initial state is "started" that we would want that status changed to 0.

Idea priority Medium
  • Admin
    Alasdair Nottingham
    Jun 24, 2022

    Thank you for the suggestion. The purpose of the prometheus endpoint is to gather performance metrics for the runtime we do not believe the request fits within the purpose of the prometheus endpoint. Given that we don't think this is a good fit for a performance feature we are declining this request. If you would like to discuss this decision further, please contact Graham Charters <>.