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)
try/catch in Impact Policy should give full stack trace
When writing Java Script Impact Policies I noticed the following:In the below code example Log(error.stack) seems to only output a truncated stacktrace, which isn't really much use in debugging. I see that I can use error.message,but that does not...
Enhancement to the scope-based event grouping extension to allow customization on the minimum number of traps for a synthetic event to be created. For example having grouping on a single trap doesn't really provide much benefit to end users. Addi...
NOI Event Analytics - The Pattern filter is not automatically filled with configuration sql filter
System: Netcool Operations Insight - Event AnalyticsActor: In Event Analytics user wants to edit the suggested pattern Description: When we go to edition page the previous SQL filter used on the Analytics configuration isn't replication on patter ...
Description: We require a KAFKA Data Source Adapter to interface with external and internal systems. NFV vendors are providing KAFKA Message Bus as the interface of choice for new elements and / or applicationsUse case: Publish and subscribe to to...
nco_g_xml_11 allow using only @ServerSerial or @ServerName as value for ate.XMLGateway.MessageKey property.We need to use at leas the combination of the both fields (for example: @ServerName+to_char(@ServerSerial)) or any other field from Objectse...
Make Message Bus Probe HTTP Responses more visible in Probe Logs
If the Message Bus Probe receives too large payloads, the sender will get back the HTTP status code "413 Payload Too Large". This is correct, but in the Probes logfiles this is only documented with a warning line "payload to large".
Does Predictive Insights supports RHEL 8.3 or 8.4?
Customer requirement is to migrate PI to RHEL 8.3 or RHEL 8.4 which is not supported currently. As of now, PI supports till RHEL 7.9. Please we need a support for PI to be supported on RHEL 8.3 or RHEL 8.4
Do not place IBM confidential, company confidential, or personal information into any field.