[lttng-dev] Duplicate traces in multiple sessions

[Jeffrey Chen]

Hi LTTng community:


We are using LTTng to collect traces from our non-stopping service (our service is running 24/7, highly available). We collect traces by rotate the trace in an interval. We do this by creating new session, stop the old session, and process the old traces, every 10 minutes.
There are overlaps on the session since we create new session before stopping the old session. We are seeing some traces exist in both the old session, and new session. This is expected. We also noticed that these duplicated traces could have slightly different timestamp in the two sessions, so it is very difficult to do post-processing to remove the duplicates.
Assuming we could read the raw binary trace files, we would like to know whether this is any way to identify the duplicating traces. Is there any kind of unique id or hash that could be used to identity the duplicate traces in two sessions?


Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20160620/358a3acf/attachment.html>