gliderlabs / gliderlabs/logspout
Question: Backlog tail, http module and device restarts?
- Dominant language
- Go
- Stars
- 4.7k
- Forks
- 661
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the logspout http module from a custom logs container and have an IoT device scenario where the host is restarted.
After the restart I was thinking I'd get container backlogs when hitting the logspout http endpoint for the first time after restart. It appears I only get the logs streamed while logspout is running so important logs during host shutdown and startup are missed.
Is there a way to get these logs with logspout in this scenario?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the logspout http module and its HTTP endpoint behavior with Docker container logs. Determine whether logs from host shutdown and startup can be retrieved after a restart, and document or implement the supported approach if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100