-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Comments
It seems like this would require a new |
Maybe. Basically a pipe can be read like a log file, but no offset should be recorded in the registry I think. |
Here: #2246 |
I need this, too. |
Yes, I would find this handy too. |
Could this be used to grab Journald logs ? Like : Filebeat :
|
This would solve a problem of mine as well. |
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. |
I would be interested in such feature too... Had some progress done already for this ? |
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. |
Good to know, thanks for your answer :-) |
Need this feature as well. |
readding from pipe could be a solution for filebeat not reading compressed files (.gz). |
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. |
This issue doesn't have a |
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
The text was updated successfully, but these errors were encountered: