vectordotdev / vectordotdev/vector
New `logstash` sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
A note for the community
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
Vector already accepts Beats inputs, but it's missing the ability to output data in this format. That would allow for:
reliable data delivery to secured Elasticsearch clusters that use Logstash input as a security layer
easier migration path from Beats + Logstash to Vector, as only one of components would need to be replaced at a time
Attempted Solutions
No response
Proposal
Add a Beats (Logstaqsh) output, supporting
TLS
compression
multiple target addresses with load-balancing
acknowledgements
References
No response
Version
No response
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 the proposal's Beats/Logstash output requirements and use cases; the issue names no source files, entry points, or tests. Done means supporting TLS, compression, multiple target addresses with load-balancing, and acknowledgements for the new output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, rust
- Domain
- backend, observability, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100