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 Filebeat to read from pipes #2242

Closed
dooblem opened this issue Aug 11, 2016 · 15 comments
Closed

Allow Filebeat to read from pipes #2242

dooblem opened this issue Aug 11, 2016 · 15 comments
Labels
enhancement Filebeat Filebeat needs_team Indicates that the issue/PR needs a Team:* label Stalled

Comments

@dooblem
Copy link

dooblem commented Aug 11, 2016

This can be considered as an enhancement.

When Filebeat is trying reading from a fifo file:
Aug 11 12:31:23 XXXXXXXXXXXXXXX /usr/bin/filebeat[20879]: log.go:103: Stop Harvesting. Unexpected file opening error: Given file is not a regular file

Old issue from Logstash Forwarder, and steps to reproduce, here:
elastic/logstash-forwarder#525

Thanks in advance,
Marc

@ruflin
Copy link
Contributor

ruflin commented Aug 11, 2016

It seems like this would require a new input_type?

@dooblem
Copy link
Author

dooblem commented Aug 11, 2016

Maybe. Basically a pipe can be read like a log file, but no offset should be recorded in the registry I think.
You may forget this issue, as I seem to be the only one to need this. And this is to work around that:
https://discuss.elastic.co/t/can-filebeat-watch-for-new-files-created-in-a-directory/57811/1

@dooblem
Copy link
Author

dooblem commented Aug 11, 2016

Here: #2246

@apelsina
Copy link

apelsina commented Oct 14, 2016

I seem to be the only one to need this.

I need this, too.

@hezor
Copy link

hezor commented Nov 22, 2016

Yes, I would find this handy too.

@meerkampj
Copy link

Could this be used to grab Journald logs ?

Like :
Journald :
ForwardToConsole=yes
TTYPath=/dev/console

Filebeat :
filebeat.prospectors:

  • input_type: fifo
    paths:
    • /dev/console

@vacri
Copy link

vacri commented May 5, 2017

This would solve a problem of mine as well.

@ruflin
Copy link
Contributor

ruflin commented May 9, 2017

I'm currently finally refactoring the prospector part which will allow additional prospectors. This is good news for this feature request above as it should make it much easier to add (potentially). If someone is interested to contribute it, ping me here in about 1-2 weeks from now and I can point to the code parts which must be touched.

@ledav-net
Copy link

I would be interested in such feature too... Had some progress done already for this ?

@ruflin
Copy link
Contributor

ruflin commented Mar 16, 2018

Progress has been made on the refactoring and the prospectors / input or now properly separated: https://github.com/elastic/beats/tree/master/filebeat/input On the implementation of the feature itself nothing has happened but the above change should make a contribution much eaiser.

@ledav-net
Copy link

ledav-net commented Mar 18, 2018

Good to know, thanks for your answer :-)

@endlesslight0
Copy link

Need this feature as well.

@gaetanquentin
Copy link

readding from pipe could be a solution for filebeat not reading compressed files (.gz).

@botelastic
Copy link

botelastic bot commented Jul 8, 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 Jul 8, 2020
@botelastic
Copy link

botelastic bot commented Jul 8, 2020

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

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

No branches or pull requests

9 participants