TimelyDataflow / TimelyDataflow/timely-dataflow
Logging nice-to-haves
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
We are about to land a PR #92 that overhauls the logging infrastructure. This issue keeps track of desirable features that should be possible with this infrastructure, but aren't yet designed/implemented.
- re-introduce the log crate
- allow ad-hoc logging of user code (i.e. allow users of timely to produce logging streams of a type picked by them)
- support log filtering, and selectively enabling log statements
- make sure that log streams can be flushed when necessary
- remove the time crate
- determine what timestamp resolution scale is appropriate, consider using a synchronisation point between processes as the time base for the logs
- let users toggle logging for certain dataflows
Contributor guide
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 PR #92 and the logging infrastructure it introduces. Define the design for filtering logs and selectively enabling log statements, then verify that the requested filtering behavior is implemented and documented.
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