You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I have some use-cases where we require the ability of specifying multiple outputs. For example:
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.
The text was updated successfully, but these errors were encountered: