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)
Better control over snmp polling for big network devices
ITNM has two different strategies for polling interfaces depending on the use of a polling filter: - Strategy 1 (when no polling filter is defined): poll all OIDs for each interface. - Strategy 2 (when a polling filter is defined): group multiple ...
Messagebus Probe WebHook should respond with WWW-Authenticate entry in header for authentication
As defined here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication :
"RFC 7235 defines the HTTP authentication framework, which can be used by a server to challenge a client request, and by a client to provide authentication infor...
Add support for multiple ObjectServers in Runbook Automation (Netcool Impact)
Our customer is extending their Netcool landscape to integrate several sites into one centralized stack. Doing so, multiple ObjectServer (one pair per site) will be connected to this centralized approach, resulting in a need for Impact to support ...
ITM SQL Agent should optimize the SQL Server plan cache usage.
Problem is that currently plans are created for every query ( samples in attached document ) that means overhead in creating a lot of plans only used once and a waste of plan cache memory.That could be optimized to reduce the plan cache memory.
Option to disable the fragmentation of tables present under tempdb database
Related to PMR case number TS008818511 The problem is locking on the “tempdb” due to checking the fragmentation of a table or view Per customer requirement, the data collection of only fragmentation should be skipped for tempdb database.
We have had several customers requesting the gateway integration for Remedy ITSM v20. There is only this information which does not address how the existing nco_g_bmc_remedy should be configured:
Support for podman on RHEL8 for Self-hosted backend server
At this point, we are not planning to add support for hosting the Instana backend with podman. The RHEL 8 docker package has been replaced by the container-tools module in RHEL 8 and some customers do not want to install docker-ce for RHEL 8 for t...
For a NOI installation running on OCP with LDAP mode proxy, it is an absolute requirement that the users icpadmin and impactadmin must exist in the connected LDAP. The names of these users are not freely selectable, but must be exactly the same.
Do not place IBM confidential, company confidential, or personal information into any field.