vectordotdev / vectordotdev/vector
New `tail` sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
We should build a TCP server sink that clients can connect to and receive events in a streaming fashion. It should probably have a throttler built in (see #258) and potentially a way to dynamically request other sampling options.
The initial implementation can be mostly a dumb pipe, but we should plan to enhance this to support structured data and build a client that knows how to pretty print it. Further down the line, we'll want it to support tailing metrics rollups as well (think dstat).
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
No files, tests, or entry points are named. Start by locating the existing sink implementations and the pipeline's event-streaming interfaces; done would mean a TCP server sink that lets clients receive events as a basic stream, while throttling, structured data, clients, and metrics rollups remain future work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100