Lucas Bremgartner

> Thanks for the clarification. We have tried to make pipelines as modular as possible, hence we have pipelines that get combined differently; e.g assuming we have pipelines A, B,...

I would like to see #124 be merged as well, before we release Beta 2.

> Interesting idea! So I guess there are three reasons for doing the pipeline wrapping: > > * When implementing daemon mode (#94) we can prevent reloading of the non-filter...

If we decide to move most (or even all) of the packages into `internal` packages and the only non `internal` left would be the `main` package, we are in fact...

@magnusbaeck What is you conclusion on this topic? Do you still plan to move all the existing packages into `internal` package directories? If so, this will break all existing importers...

Hi @jgough Thanks for your feedback. I have fixed the issues "dash in `pipeline.id`" and "`path.config` pointing to dir in `pipelines.yml`" in #125. In order to get more debug information...

@jgough ~~I just tested an input plugin with a dash (`-`) in the name and this worked for my with #125 applied. Can you confirm, that this works for you...

The first thing, that comes to my mind is `pipeline.workers`. Have you tried to set this value explicitly to `1`?

And `pipeline.ordered` as well. See: https://www.elastic.co/guide/en/logstash/current/logstash-settings-file.html

I am not sure, if there is a solution for this problem, if `pipeline.workers` and `pipeline.ordered` do not help. LFV processes the events in the order they are returned from...