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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
IBM Turbonomic ARM
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Re-Login URL Problem in IDP Enabled Backend
Hi, When a user logout from the IDP-enabled K8/OCP-based installation, it forwards the user to the base URL to which a user can't log in. So they need to change URL to tenant again. That behaviour creates confusion on the user side. Thank you.
Self hosted backed on Docker, Support for RHEL 9.x
According to support matrix RHEL 9.x is not supported for self hosted backed installations. However vast majority of customers are using RHEL 9.x RHEL 9.x OS support required for Instana self hosted backend
Oracle E-Business plug-in - Wait for child requests
Customers use the Oracle E-business plug-in to manage individual Concurrent Manager requests as IWS jobs. Those request may submit one or more child requests to Oracle Concurrent Manager. The IWS Oracle E-Business plug-in does not currently provid...
Oracle E-Business plug-in - Selectively include concurrent program output in IWS job log
Output from Oracle E-Business concurrent programs, managed by IWS, is not currently included in the associated IWS job logs. Having the ability to selectively include the program output in the IWS job log can make it easier for Operations teams to...
Oracle E-Business plug-in - Ability to manage Request Sets
Oracle E-Business requests can be combined into request sets, where Oracle Concurrent Manager executes the individual requests in the set according to the relationships defined in the set. The IWS Oracle E-Business plug-in currently only supports ...
Application and Event monitoring statefulset operators
The community around the operator pattern and the community framework has gained a lot of traction and has matured quite a bit from its original proposal and delivery. There are increasingly more examples of technologies adopting this pattern (htt...
Operator pattern based deployment lifecycle management for the Application and Event monitoring workload
Refactor the ibm-cloud-appmgmt-prod helm chart to be replaced by a go-sdk operator for controlling the deployment lifecycle, administrative and operation tasks of the IBM Cloud App Management workload.
Note: Not to be confused with using a helm-t...
Vertical scaling of Application and Event monitoring stateful services
A means by which to effectively perform vertical scaling of key stateful services in the `ibm-cloud-appmgmt-prod` chart.
Today, the stateful services include PersistentVolumeClaims in their pod spec, and use helm values to configure the size of t...
Allow for additional inputs into the placement rules. For example: cost of resources within a cluster, network latency of a cluster (ex: edge vs central cloud), networking capacity between locations, cluster hardware capabilities (CPU pinning, GPU...
Enhanced Visibility of Deployed Application Versions.
Update the topology, application, and/or overview screens in MCM to more effectively see what release(s) of applications are deployed to which clusters. These views should be consumable even when there are 100s of clusters and support grouping by ...
When doing an application update (such as from v1.0 to v1.1) for multiple Deployables each deployed in their own cluster, the customer needs more control over how those upgrades are performed. The ability to do a canary deployment (upgrade just on...
Do not place IBM confidential, company confidential, or personal information into any field.