I was trying to use /dev/stdout as the beats output but failed to do so.
The config is like ...
### File as output
file:
# Enabling file output.
enabled: true
# Path to the directory where to save the generated files. The option is mandatory.
path: "/dev"
# Name of the generated files. The default is `topbeat` and it generates...
filename: stdout
BTW, I just hope to use /dev/stdout for easier debugging of the beats output.
@mrkschan Interesting idea. I actually never tried that. This will probably fail as the file output tries to create and rotate files which I don't think is possible for /dev/stdout. I would recommend to create a local file and tail it for debugging at the moment.
Yes, indeed. I get the same behavior. No warning is printed out. I created a bug in libbeat and it's targeted to be fixed for the next release 1.0.0-GA: https://github.com/elastic/libbeat/issues/212
@steffens that is great! Though, why -d '*' cannot catch this or do I miss something?
BTW, I'm thinking if stdout is an viable output option in libbeat. Consider the following cases:
libbeat is used in a custom beat that is required to send events offline (e.g. latency requirement, durability requirement, etc.), either file output or stdout will be used and later ship via filebeat for instance. If that beat is executed inside a Docker container, stdout would be a preferable option.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.