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)
Can we have Dual discovery or much controlled and customised discovery modes: main aim is to reduce long discovery times here.
For Ex. what we are looking for is described below:
Let us say we have seed based control not using scope based: [two seperate dedicated files]
Full discovery for any new device only Partial discovery for any changes to devices only on some important attributes like hostname / subnet / gateway / ipaddress / etc.,
each run alternative
So at this stage we need another process that manages any unmanaged or deleted or decommission device from network with every 5 mins [customisable] cycle, basically what it does is go see if device exist just disable from any thing like discovery / polling / event processing / topology visualisation and etc., with some flag in NCIM DB
So device does exist for some 30 days [customisable] and get deleted automatically from all in-memory / NCIM / cache db files, without any manual process [not using ingress which is bit hard to manage with this new solution / enhancement request]
so this decomm / delete device will show in reporting as no loger active some thing but show some data up until active [STORM flow]
Do not place IBM confidential, company confidential, or personal information into any field.