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)
NPI supports setting a threshold value for a metric that will result in an Alarm raised when that threshold is crossed. This allows to take an action when the system is degraded. Current implementation allows to set a threshold value for each metric that is being collected by the system. This has the limitation that you can not set different thresholds for the same metric for different equipment. For example, you will need to take action in a more proactive way depending on the SLA of the customer. Normal values might differ depending on the equipment (for example, normal values for Optical Power will be different depending on the distance of the link between equipment. In order to take full advantage of this functionality and set more useful ranges to trigger alarms, it would be necessary to set a threshold not only for a metric, but for a metric AND an interface.
In order to set the threshold, the user of NPI will have the option to select a metric and set the threshold value for the metric, as it is today.
It will also have the option to select an interface and a metric and set the threshold for the combination of both.
When a metric is updated, the system will first check if there is a threshold for this metric and the interface, and trigger the alarm accordingly.
In case there is no threshold set for the metric and the interface, it will check for a default threshold (the same as current functionality) and trigger the alarm if this generic threshold is reached.
The generic threshold is only check if there are no threshold specific to the interface.
Do not place IBM confidential, company confidential, or personal information into any field.