Nomad monitor include backlog of recent messages
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
`nomad monitor` starts streaming new log messages after the monitor process starts.
When diagnosing issues it could be helpful to include a backlog of messages. Either add an option to configure a backlog of messages or just adjust the monitor sink to always include a backlog of messages.
Ability to configure inmem backlog size (500kb, 50mb)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the `nomad monitor` command and its monitor sink, then inspect how the in-memory backlog is configured. Decide whether the backlog should be configurable or always included, including the stated 500kb and 50mb sizes. Done means recent messages appear when monitoring starts and the selected backlog behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100