-
Notifications
You must be signed in to change notification settings - Fork 148
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
[8.x](backport #5672) Add filebeat receiver to otel mode #5693
Conversation
* Add filebeatreceiver to otel components (cherry picked from commit bd219d6) # Conflicts: # NOTICE.txt # go.mod # go.sum
Cherry-pick of bd219d6 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 |
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request has not been merged yet. Could you please review and merge it @leehinman? 🙏 |
1 similar comment
This pull request has not been merged yet. Could you please review and merge it @leehinman? 🙏 |
closing. new PR will happen in Main. |
8.x
.What does this PR do?
Adds filebeat receiver as an otel receiver.
Why is it important?
This is the first beat receiver, and this will allow us to test the feasibility of running beats as otel receivers.
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
should be 0 user impact of existing configurations
How to test this PR locally
Use something like the following as
otel.yml
, and runelastic-agent otel --config otel.yml
This will run the beat receiver, which will produce one event.
The event should be written to the path you specify in the
file/no_rotation
section.Related issues
Questions to ask yourself
This is an automatic backport of pull request #5672 done by [Mergify](https://mergify.com).