Time stamp of the LOG is not exactly when the log generated.
- Dominant language
- C
- Stars
- 459
- Forks
- 340
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 2
Description
### Discussed in https://github.com/COVESA/dlt-daemon/discussions/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
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported sequence with dlt-receive: generate delayed logs, stop reception, wait, restart it, and compare the displayed timestamps with generation times. Then trace where dlt-receive obtains timestamps and document whether the behavior is intended or identify the entry point needing correction. Done means the timestamp semantics are clarified and, if it is a bug, verified against the reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100