Andrew Cholakian

@fluency03 this is where it gets so challenging. Where should we store it while we wait? The local FS, somewhere else? What would your preference be? I'm thinking the best...

@wadejensen are you aware of the upcoming multiple pipelines feature in 6.0? Does that change things? https://www.elastic.co/guide/en/logstash/master/multiple-pipelines.html On Nov 4, 2017 12:51 AM, "Wade Jensen" wrote: > @jordansissel Thanks for...

https://github.com/elastic/logstash/pull/9225 may address the concerns raised in this thread. Would that approach be useful to those of you facing this issue?

I've opened https://github.com/elastic/beats/issues/27648 to discuss what our path forward here is. At the very least we need to improve docs.

Hey, thanks for taking a look into it. @mlimotte I'll try and find some time to fix the AMI with your patch.

@NoodlesNZ sorry, but I don't have time to maintain this anymore. Feel free to fork it however!

Ah good catch, yeah, it's not restoring correctly.

This is actually a UI bug. So, engulf only stores the final result in the interest of space (it used to store them all, but I decided against keeping that...

FWIW in 'live' mode, you see jobs started by anything, whether it's you, an API client, or another browser. There needs to be some way of getting into live mode...

I'm gonna revise the spec, instead of uploading a file you'll be available to specify the URL of a file which workers can download and run against.