Question & Answer
Question
Generic Clear : Why are same-second problems not being resolved?
Cause
In Netcool/OMNIbus v7.3.1 : The default behaviour of the generic_clear trigger is to leave problems and resolutions in the same second alone.
LastOccurrence < resolution.LastOccurrence
Answer
For a solution in the multitier environment see the Support's Guide to Sub-second Events in a Multitier Environment.
For general guidance and example solution read-on:
Although Netcool/OMNIbus takes into account the same second sequence at the probe level using ProbeSubSecondId, it does not provide a complete solution for handling same second events within the Netcool/OMNIbus system.
Support's guide to sub-second triggers provides a set of scripts that allows the configuration of an object server to be performed easily, so as to demonstrate the logic required to implement a sub-second solution with a production environment.
Within the guide the default behaviour is discussed, and how to update the object server to cater for sub-second events, through the creation of a custom generic_clear trigger. This solution is suitable for a multitier environment, with the generic_clear being placed at the Aggregation layer and the Collection object servers forwarding the required sub-second fields..
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21591539