-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Support logstash as an output type in API and Kibana config #125990
Conversation
2715805
to
ab55cb8
Compare
ab55cb8
to
c7db63b
Compare
Pinging @elastic/fleet (Team:Fleet) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
x-pack/plugins/fleet/common/openapi/components/schemas/output.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested functionality, looks good on UI
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Public APIs missing comments
Page load bundle
Saved Objects .kibana field count
History
To update your PR or re-run it, just comment with: cc @nchaulet |
Summary
Resolve #125792
Add support for logasth type in Fleet ouput API and preconfiguration.
The logstash output require the host to not contains the schema, and allow to configure SSL options.
That PR add a new
ssl
key to the output saved object that is not indexedTest
The API changes are covered by API integration tests
How to test
You can create a logstash output by adding the following in your Kibana config
You should see the output correctly created in Kibana and used in the agent policy (it's not editable for now the UI will come in a following PR)
@lykkin This should allow us to start E2E testing with the Agent.