Improve log timestamps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
It seems the log timestamps are based on when they are ingested vs when they actually happened. In my case there's big 2 minute jumps which made me think my server had a bug. Attached my log file which has the Dokploy timestamps vs my server's timestamps.
mediacreatorprogrpc-api-ipdh5m.1.iy4bpijw19xb0tqk9vj5koyer-20250911_042648.log.txt
Describe the solution you'd like
Preferably this would use the timestamps from docker
Describe alternatives you've considered
The ingestion interval being 10s or lower could also be acceptable
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the attached log's Dokploy and Docker/server timestamps, then locate the log-ingestion path that determines which timestamp is displayed. Done should mean displayed log times reflect Docker event times, or ingestion delays are consistently limited to the proposed interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100