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)
Have EventGateway to associate symptom Events to Root Cause Events by using @ServerSerial-@ServerName instead of @Serial
In an environment with ITNM connected to a Helper ObjectServer Pair, the Event Gateway is associating the Symptom events NmosSerial with the Serial Number of the Root Cause event in the Helper ObjectServer, this causes the Root Cause to Symptom events relationship not to be able to find and correlate the events in the Aggregation/Display ObjectServer pair, since Agg/Display has not visibility over the events in the Helper ObjectServer Pair.
By having just the Serial of the active Aggregation ObjectServer, can potentially cause the same problem if the Primary ObjectServer gets inactive and the Secondary ObjectServer is the one connecting to the EventGateway.
A solution for this would be to use @ServerSerial/@ServerName combination since those don't change during the event's life Cycle.
In a three tier ObjectServer architecture with 2 or more collection ObjectServers and 2 Aggregation ObjectServers, the @Serial field is assigned by the local ObjectServer processing the event, in Aggregation, the Primary ObjectServer @Serial is different to the Secondary ObjectServer @Serial.
The EventGateway assigns @NmosSerial the @Serial of the ObjectServer the gateway is currently connected to, if the ObjectServer becomes unavailable and the AGG does a switchover from Primary to Secondary, then the association is lost.
@ServerSerial and @ServerName are kept consistent through the Event's lifecycle.
Do not place IBM confidential, company confidential, or personal information into any field.