beats filebeat can support pulsar input/output

Pulsar is a message middleware, and some companies have switched from Kafka to Pulsar. When can Pulsar input/output be supported?

Jun 25 '24 08:06 azeng528

This issue doesn't have a Team:<team> label.

Team: middware

Jun 25 '24 09:06 azeng528

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

Jun 26 '24 01:06 elasticmachine

Just noting that this request has been brought up before as well: https://github.com/elastic/beats/issues/31963 (same user), https://github.com/elastic/integrations/issues/3644 (same user), https://github.com/elastic/beats/issues/19476 (different user).

Jun 26 '24 01:06 ycombinator

There is a PR in progress here: https://github.com/elastic/beats/pull/37552 This one is now in conflict and needs to be fixed by its creator.

Jun 26 '24 07:06 pierrehilbert

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

Jun 26 '25 07:06 botelastic[bot]

Closing, we are going to support running Beats as OpenTelemetry collector receivers and the path forward will be to use the collector's pulsar exporter once that is ready.

Jun 27 '25 15:06 cmacknz