vectordotdev / vectordotdev/vector
Add support for "peeking" at long server responses in sinks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Ref PR #2185 discussion starting at this comment
Some servers, notably Elasticsearch, can produce large responses to queries, in some cases larger than the transmitted data. To avoid this becoming a resource drain in Vector, we should only load a fixed size response into memory, and then load the remainder if it is actually needed.
More investigation is needed on this issue to see how big a problem this actually is.
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 with the discussion linked from PR #2185 and investigate how sinks currently load server responses, especially responses from Elasticsearch. Determine whether fixed-size peeking is needed and define the conditions for loading the remainder; the issue is complete when the scope and expected behavior are established and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, rust
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100