-
Notifications
You must be signed in to change notification settings - Fork 5k
[8.19](backport #47693) [beatreceiver] Do not require specifiying otelconsumer output #47716
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
base: 8.19
Are you sure you want to change the base?
Conversation
* do not require explicit config (cherry picked from commit b80d1e9) # Conflicts: # x-pack/filebeat/fbreceiver/receiver_test.go # x-pack/filebeat/tests/integration/otel_lsexporter_test.go # x-pack/libbeat/cmd/instance/beat.go
|
Cherry-pick of b80d1e9 has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
@khushijain21 could you please fix the conflict? |
|
This pull request has not been merged yet. Could you please review and merge it @khushijain21? 🙏 |
Proposed commit message
All beatreceivers will use otelconsumer output by default and it does not require us to specify this explicitly.
Checklist
stresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.Disruptive User Impact
None
Related issues
This is an automatic backport of pull request #47693 done by [Mergify](https://mergify.com).