clockworklabs / clockworklabs/SpacetimeDB
Implement limit and rolling logs for module_logs (10 GB max)
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
We had an issue in live with a large number of module logs. We should limit the max size of module logs. Basically a TTL-like system
Contributor guide
No contributing guide indexed for this repository
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 tracing how module_logs are stored and managed; the issue does not name a file or test. Define how the 10 GB maximum and TTL-like rolling behavior should work, then verify that old logs are removed and the limit is maintained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100