key-value logging
- Dominant language
- Rust
- Stars
- 98
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Now that experimental key-value logging has landed in `log` (https://github.com/rust-lang-nursery/log/issues/328), we should look into using it for `async-log`.
This is currently blocked on having a way to actually _log_ key-value entries, as the macros in `log` don't support this yet. I've asked a question about this in https://github.com/rust-lang-nursery/log/issues/328#issuecomment-513557680, which hopefully lead to a resolution where we can start logging key-value pairs!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked log issue #328 and its key-value logging discussion, then inspect async-log's logging macros and entry points. Confirm how log will expose key-value entries before proceeding; done means async-log can emit those pairs through the resolved log API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100