You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
still to do:
- support async go-lumber client
- support bulk_max_size
- support windowing
- support load balancing
- support backoff
- determine if codecs are needed
Closeselastic#129
* 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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: