This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including 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.
Do not place IBM confidential, company confidential, or personal information into any field.