Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Oct 14, 2019

Message Bus Probe should expose endpoint to Rules File

Follow up for RFE 126508 / APAR IJ17178:
Great that we now have the Sender of the request and that we no longer need to specify a fixed endpoint.
But unfortunately, the endpoint (or the full URL) is not available as a Token variable in the rules file.
So we still cannot easily determine in the rules file where the request comes from. (Yes, we do have the IP address, but that may vary, whereas the endpoint will remain the same for a specific
software sending the event).
Please make the endpoint available as a token - its already available in the debug log !

Idea priority Medium
RFE ID 137259
RFE Product Tivoli Netcool/OMNIbus Probes
  • Guest
    Jul 19, 2023

    Er, we missed the mark on this one.. and in a wildly curious fashion.

    The point of this enhancement request was to expose the endpoint that the probe was exposing, and that the source was using. That is... if you understand how the json parser file works, you can have multiple endpoint definitions that the probe will respond to. The idea here is that a customer could have multiple endpoint definitions for different event sources, and then in the rules file they should be able to switch against the endpoint, and handle alarms differently based on whatever endpoint was used.

    In my testing, the endpoint is NOT exposed in the $(MESSAGE.META.MSG_ENDPOINT) token. But rather, the URI is exposed and a UUID is tagged on the end of the URI. That UUID is the same irrespective of what endpoint (as defined in the parser config). This is not useful at all.

    The $MESSAGE.META.MSG_ENDPOINT must expose whatever ENDPOINT was used (as defined in the parser config) to ingest the message.

  • Guest
    Jul 7, 2023

    This enhancement is available in the latest the Probe for Message Bus.
    To obtain the package, use the part number mentioned in the release notice:

  • Guest
    May 5, 2023

    Although the status is "Planned for future release", this has been made available in version 22 of the MB-Probe.

    The endpointis available in token $(MESSAGE.META.MSG_ENDPOINT)