Time stamp of the LOG is not exactly when the log generated.

[Praveen1448]

Discussed in #723

^{Originally posted by Praveen1448 December 20, 2024}
When trying to read the Logs time stamp, the time stamp we get is when we see the Log(with dlt-receive), but not when the actual log is generated. is this how it works? or else is there any way to get the actual time stamp of when the log got generated?

as you can see I have made the logs to generate with a delay of 1 sec. when the 11th log(red box) is generated the time stamp is 10.28.02(yellow box) and I have stopped the dlt-receive waited for 1 min and started the dlt-receive again, then the 12th log's(blue box) timestamp is 10.29.08(green box) but here the actual log is generated on the time of 10.28.03 but the log timestamp is the time when I started the dlt-receive.
is this how you intend to implement it? or else do we have any other way to get the actual time stamp of the log generated please help me with it?
@minminlittleshrimp @lti9hc

[lti9hc]

Hello @Praveen1448,

This is a bug and currently used timestamp of dlt-receive
We will deliver the fix

[mse-kondou-hitomi]

Hello @lti9hc .

I believe this issue applies not only to dlt-receive but also to offline log storage.
Will the dlt-daemon be fixed at the same time?
In the following section of the source code, I think it is correct to overwrite only the ECUID.

dlt-daemon/src/daemon/dlt_daemon_client.c

Line 371 in c5fc99c

if (dlt_set_storageheader(daemon_local->msg.storageheader, ecu_ptr)) {

[minminlittleshrimp]

Yes, an investigation is needed here. dlt_get_timestamp from where and how the timestamp is implemented is not our concept but from old long dev history.