Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Implement the Logstash output #129

Closed
Tracked by #197 ...
cmacknz opened this issue Sep 26, 2022 · 1 comment · Fixed by #210
Closed
Tracked by #197 ...

Implement the Logstash output #129

cmacknz opened this issue Sep 26, 2022 · 1 comment · Fixed by #210
Assignees
Labels
8.6-candidate Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@cmacknz
Copy link
Member

cmacknz commented Sep 26, 2022

The same as #10 and #116, but for Logstash.

The agent supports a Logstash output today, so the shipper must implement a Logstash output to maintain feature parity with the outputs already available today.

Acceptance Criteria

  • An integration test exists proving that the shipper can communicate with Logstash.
  • An end to end test exists proving the agent can configure the shipper to communicate with Logstash.
  • At least manual performance testing of the Logstash output has been performed.
@jlind23
Copy link
Contributor

jlind23 commented Jan 5, 2023

@leehinman any PR to provide here? Saw you made some progress on your fork.

leehinman added a commit to leehinman/elastic-agent-shipper that referenced this issue Jan 5, 2023
still to do:
- support async go-lumber client
- support bulk_max_size
- support windowing
- support load balancing
- support backoff
- determine if codecs are needed

Closes elastic#129
@leehinman leehinman mentioned this issue Jan 5, 2023
4 tasks
leehinman added a commit that referenced this issue Jan 17, 2023
* POC for logstash output

still to do:
- support async go-lumber client
- support bulk_max_size
- support windowing
- support load balancing
- support backoff
- determine if codecs are needed
- update default config

Closes #129
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
8.6-candidate Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants