-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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] Do not allow to use logstash output with APM integration #125994
Comments
Pinging @elastic/fleet (Team:Fleet) |
Don't we need to do something similar for policies with a Fleet Server integration policy? cc @mostlyjason |
I think Fleet server should be able to run with a policy with a logstash output as we pass the ES output as an argument to Fleet server with |
yeah, fleet server doesn't actually get its output information from the usual agent pipeline. not sure if it's being tracked, but endpoint also doesn't support logstash and should be treated similarly. |
@brian-mckinney is working on the implementation for endpoint so it should not be a problem. |
Hi @nchaulet
Build details: Hence marking this as QA:Validated. |
Hi @nchaulet
Please let us know if we are missing anything |
Hi Team Thanks |
Description
Related to #104987
The APM integration is not compatible with the logstash output type we should not allow user to use a logstash output with that integration.
Test plan
The following scenarios should be covered:
The text was updated successfully, but these errors were encountered: