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)
Improving of prediction taking into account the hierarchy of the network
It is necessary for PI to take into account the hierarchy of the network in order to provide more accurate information about relationships between metrics.
Currently, PI prediction is based only on mathematical model and doesn't use topological relationships which cause that PI gives some metrics as related to each other, which can't be related, as they are from different Cells, that have different parent BSCs, from different cities, different domains or even technologies...
Some of the suggested method of supplying relationship information could be: 1. Manual entry of rules to force a relation to form or to NOT form and thus avoid linking metrics from a variety of resources that are not related to each other. 2.Manually add rules that will calculate the distance between entities by having information about entity's position and thus prevent the linking of metrics that originate from entities that are very distant and not related. 3.Import a network topology and then only allow causal relationships between items that have the same parent, grand parent, grand grand parent etc.
Do not place IBM confidential, company confidential, or personal information into any field.