Logging oversaturation and file spread
Open
challenging first issue
CLI
deployed version
- Dominant language
- Python
- Stars
- 13
- Forks
- 17
- Avg merge
- 6h 59m
- Merged PRs (30d)
- 1
Description
> [!NOTE]
> Migrated from [augurlabs/augur#3008](https://github.com/augurlabs/augur/issues/3008)
> Originally opened by `@cdolfi` on 2025-02-20
---
It can be hard at times to debug because the logs can not be kept for long as 1000s of jobs generate 100s of lines of stack trace, all at once after a potential useful error log (like index corruption messages) has passed. There might be a design problem/change that would help the useful logs be able to stick around longer. @GregSutcliffe tagged to provide more context and lmk if I should edit this description
Contributor guide
Assessment
This issue has not been assessed yet.