Using pipes with Retis has been discussed in a few cases, e.g. #489 and #454. This would allow more flexible uses, to allow using external tools for handling events (both at collect and post-processing time).
For this to be possible, Retis should play nicer with UNIX pipes. Some testing and investigation is required. At least one known issue is the use of seek while reading files at post-processing time. But also the UX might be improved to avoid having to explicitly use /dev/stdin as the input file name.
Using pipes with Retis has been discussed in a few cases, e.g. #489 and #454. This would allow more flexible uses, to allow using external tools for handling events (both at collect and post-processing time).
For this to be possible, Retis should play nicer with UNIX pipes. Some testing and investigation is required. At least one known issue is the use of seek while reading files at post-processing time. But also the UX might be improved to avoid having to explicitly use
/dev/stdinas the input file name.