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,
Post an idea
Upvote ideas that matter most to you
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 notifications 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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 !
One single probe as receiver for Promotheus and Grafana; Rules file has a switch/case based on the enpoint
Do not place IBM confidential, company confidential, or personal information into any field.