Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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
Categories Integration
Created by Guest
Created on Apr 1, 2024

Capture the JVM Name in Synchronous API Tracking instead of only server name

With MAS, the synchronous API tracking is going to show only the server name which will be something like MXServer for all JVMs. That makes it impossible to correlate to the specific JVM that handled the traffic. For example, if I have 6 UI pods, I want to distinguish which specific UI pod handled the REST API request to get the logs for an error that occurred.

In the server sessions table, we track a javajvmname field that indicates exactly which POD correlates to that server session entry. We would like to see the synchronous API tracking capture this information instead of the generic MXServer for all requests.

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Admin
    Lisa Stuckless
    Reply
    |
    Aug 19, 2024

    Part of 9.0 release to use pod name instead of mxserver name for sync message tracking

  • Guest
    Reply
    |
    Jul 2, 2024

    Even if the IP Address were added, you could at least look up the Pod ID using ServerSession.