Skip to content
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

Allow for multiple outputs in filebeat #42957

Open
hartfordfive opened this issue Feb 27, 2025 · 1 comment
Open

Allow for multiple outputs in filebeat #42957

hartfordfive opened this issue Feb 27, 2025 · 1 comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label

Comments

@hartfordfive
Copy link
Contributor

I have some use-cases where we require the ability of specifying multiple outputs. For example:

  • shipping logs to a topic on two different kafka clusters
  • shipping logs to a kafka topic as well as writing them to a file

I'm aware, this has already been discussed in this issue but was made clear at the time there were no plans on adding it. In our case, we definitely don't want to have multiple instances of filebeat running just a accomplish this as it's much cleaner and simpler to manage it via a single running application. Also, when it comes to monitoring each of these potential filebeat instances, each of them would require its own port for exposing the HTTP server to fetch metrics from it. Working in environments with stricter security requirements where ports need to be pre-approved and opened by another team on a central firewall, this makes releasing any new filbeat instance quickly very painful.

We do have other potential filebeat replacements that could use to allow for this feature (Logstash is out of the question unfortunately) although I would prefer using filebeat seeing it's already deployed on hosts.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 27, 2025
@botelastic
Copy link

botelastic bot commented Feb 27, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

No branches or pull requests

1 participant