Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.17.0
-
None
-
Moderate
Description
I've found some code in a route that writes a message to a file with `fileExist=Append` as an option.
To my surprise it first goes through a processor that adds a newline character to the end of the text message. It seems our reader (Logstash) requires one-message-per-line in it's input files.
Of course, if we re-pointed ourselves at a message broker instead of file: the newline-appender processor becomes redundant and thus our code would need to change so it doesn't feel right at all.
If we had a `appendChars` option we could do `&appendChars=\n` instead on the file endpoint uri which feels more natural.