If you look at patch https://git.eclipse.org/r/139675
, the tie-breaker when timestamps are equal is the stream filename alphabetical order. It does not guarantee creation order, but at least it guarantees a predictable order.
To have some other order I think would involve:
- add custom extra attribute to the trace event, and add ability in CTF parser for the user to provide a custom tie-breaking comparator
- define some standard tie-breaking extra attribute in CTF events that would apply for all, and update CTF parser with a corresponding tie-breaking comparator
We can investigate if any of these solutions are possible.
In the meantime, just an idea, you might be able to do something in your trace by using a different clock frequency? For example if the CTF timestamps are in picoseconds maybe you can use the last 3 digits as some kind of sequence number? Then to prevent timestamp overflow you can set a clock offset in the trace metadata.