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

[Filebeat] set output in prospectors section #6531

Closed
yodog opened this issue Mar 12, 2018 · 7 comments
Closed

[Filebeat] set output in prospectors section #6531

yodog opened this issue Mar 12, 2018 · 7 comments
Labels
enhancement libbeat needs_team Indicates that the issue/PR needs a Team:* label Stalled

Comments

@yodog
Copy link

yodog commented Mar 12, 2018

as per https://discuss.elastic.co/t/two-filebeat-instances/123132 i believe it would be of benefit if we could set the output on a prospector basis instead of a global, yml wide, output.elasticsearch or output.logstash

currently i have two instances of filebeat running, one for each output, that could easily be set like below:

filebeat.prospectors:

- type  : log
  output: elasticsearch
  paths :
    - /opt/zimbra/log/mailbox.log

- type  : log
  output: logstash
  paths :
    - /var/log/myapp/*/*.log

or

filebeat.prospectors:

- type: log
  output.elasticsearch:
    enable: true
    hosts : ["localhost"]
  paths:
    - /opt/zimbra/log/mailbox.log

- type: log
  output.logstash:
    enable: true
    hosts : ["host.domain"]
  paths :
    - /var/log/myapp/*/*.log

@zvanderbilt
Copy link

I would also like to see this feature implemented

@danky78
Copy link

danky78 commented Jun 17, 2019

I would like to see this implemented too

@muraveynovosibirsk
Copy link

@jaredj
Copy link

jaredj commented Sep 24, 2019

👍

@yodog
Copy link
Author

yodog commented Dec 27, 2019

[Agent] Add support for multiple outputs for the Beat agent.
#14445

@botelastic
Copy link

botelastic bot commented Nov 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added Stalled needs_team Indicates that the issue/PR needs a Team:* label labels Nov 26, 2020
@botelastic
Copy link

botelastic bot commented Nov 26, 2020

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

@botelastic botelastic bot closed this as completed Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement libbeat needs_team Indicates that the issue/PR needs a Team:* label Stalled
Projects
None yet
Development

No branches or pull requests

6 participants