vectordotdev / vectordotdev/vector
Polish and release `tracing-limit` as its own crate
Open
Nobody has claimed this yet.
domain: observability
meta: idea
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
We should polish tracing-limit and release it as its own crate to give back to the ecosystem.
Blockers
We need to figure out how we want to expose the rate limiting setting. I will follow up with the direction the tracing team decides to go in.
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 locating the existing tracing-limit implementation and reviewing the tracing team's decision on how to expose the rate-limiting setting. Done means the crate has been polished and released independently, with that API direction resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100