@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.
- libbeat is used in a custom beat that is required to send outputs to stdout according to the ops team so that it can be integrated with syslog easily (there's some good reason behind this - https://hynek.me/articles/taking-some-pain-out-of-python-logging/).
- straight forward debug / development option.
Though I know that I make up these cases, libbeat as a library may not prevent a common output option - stdout.