luckyframework / luckyframework/dexter
Grouped Logging feature
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 21
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
When you log a bunch of asynchronous code, it gets logged out of order which leads to some confusing logs. To go along with https://github.com/luckyframework/lucky/issues/950#issuecomment-617433176, one thing we could do is queue up everything that needs to be logged, then log the queue all at the same time.
This could also be along the same lines as https://github.com/luckyframework/dexter/issues/38 where using dexter becomes a queue center for logging and special formatting. Then you can use the standard Crystal Log for lower level control.
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 reviewing Dexter's existing logging flow and the linked Lucky and Dexter discussions about asynchronous and queued logging. Clarify the queueing, ordering, formatting, and relationship to Crystal Log before implementing anything. Done should be defined as a concrete grouped-logging behavior with tests for asynchronous output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100