Lucas Bremgartner

I am not sure, if it would be be considered a bug by the Logstash team, that logstash does not exit with a non 0 exit code in this case....

I had an other look on this issue. My above analysis is wrong. The exception is thrown in the `register`method of the plugin and therefore you (@magnusbaeck) are right, logstash...

According to https://github.com/elastic/logstash/issues/6712#issuecomment-320282308 this should be fixed in Logstash. But I did not test it again.

@choffee The 20 seconds are because of the slow Logstash startup time. Do you already use the possibility to have multiple `input` and `expect` in the same test case file?...

@choffee Good the hear that you like the new option. I'm thinking about to speed up LFV even more, but this is not yet ready.

This might be related to #149. The generator input approach does not work well for cases with codecs as well as with inputs that have "special" characters (from the Logstash...

*x* input lines can lead to *y* input events can lead to *z* output events There is no direct relationship between: * the number of lines of input * the...

In #156 I currently have a version, which handles multiline codec better and also correctly maps the fields to the correct input by having a separate input plugin for each...

It is correct, that currently the field `host` is always removed, if this field is set via `input` and codec (https://github.com/magnusbaeck/logstash-filter-verifier/blob/master/internal/daemon/session/files.go#L48). It is for sure debatable, if this is the...

@nicolasreich It would be great, if you could provide a PR for the updated documentation. With the change in PR #156 the following fields are removed by default: * `host`...