vectordotdev / vectordotdev/vector
Granular logging for sources, transforms and sinks by tracing span
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
As a user, I want to be able to set customized logging levels for each stage of the pipeline to get a full picture of what each stage is doing. We currently support enabling logs by call site (aka by Rust module), but being able to enable them by tracing span would ensure that can set a log level for a given component and any shared modules that component is usig will also have the same log level.
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 examining how Vector currently enables logging by call site or Rust module, then trace how sources, transforms, and sinks are represented. Define the behavior for assigning logging levels by tracing span, including shared modules used by a component. Done means each pipeline stage and its shared modules can be controlled through its span-level setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100