-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[libbeat] Introduce Apache Pulsar to beats as an output plugin #37552
base: main
Are you sure you want to change the base?
Conversation
💚 CLA has been signed |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
This pull request is now in conflicts. Could you fix it? 🙏
|
/test |
# Conflicts: # go.sum
@ycombinator Resolved, but there is an error |
It means the |
Oh, yes, I remember now, since this PR pending for a long time, I forget I need to update the NOTICE.txt file |
@ycombinator It seems the ci checks passed, can we keep going on the PR? |
buildkite test this |
This pull request is now in conflicts. Could you fix it? 🙏
|
|
# Conflicts: # NOTICE.txt # go.mod # go.sum # libbeat/publisher/includes/includes.go
@ycombinator @pierrehilbert @cmacknz Can you please help trigger the tests and merge the PR? |
/test |
This pull request is now in conflicts. Could you fix it? 🙏
|
@dao-jun thank you for this excellent PR. We actually plan on using Otel exporters for new beat outputs and it looks like you are the maintainer for that code as well https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/pulsarexporter In future releases of the Elastic Distribution of the Open Telemetry Collector (EDOT) we plan on introducing the ability to run beats as OTel receivers. https://www.elastic.co/guide/en/fleet/current/elastic-agent-cmd-options.html#elastic-agent-otel-command |
Does it mean that we don't need this PR anymore? |
Proposed commit message
Introduce Apache Pulsar to beats as an output plugin, and users could send data to Pulsar.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs