Additional Timestamping Options for Alarm Grouping

Needed:
IBM/TELUS needs to develop a strict timestamping protocol to capture alarms as they move through the stack: Probes, Collection, Agg, ToCEA, Kafka, fromCEA,  etc.

Expectations:
We want the application to provide alarm grouping in real/near time.

Issues:
Alarm grouping is highly corrupted by delays.  With the current timestamping protocol it is extremely difficult to identify where delay bottlenecks are manifesting and disappearing.  The end result is broken grouping logic.  The collator pod is presently at capacity with its roles and functionality, it is very likely we need an addition pod to handle "time administrative" duties.

Geraldine M.  provided an elegant verbalization of what is required.  

Needed:
The proposed solution involves adding a new column(s) to base finalization on event arrival time, not first occurrence time. Yasser Abduallah suggested using a new, universal column name for this arrival time.

Summary:
Our primary expectation of ASM/AIOps is in velocity of alarm correlation, with current bugs and inconsistencies in grouping caused by time issues the confidence in the application is diminishing and exposed to alternative solutions.  We don't want that hence the request to have a more elegant solution ... solutioned.  This RFE is an attempt to have IBM formally address the timing anomalies in alarm grouping.