Consider logstash configuration useability

[mwl]

I don't know the right answer. But using CLI parameters to alter the logstash config seems clunky. It's not immediately obvious to users who are used/have read that you use a configuration file.

Consider allowing the use of a configuration file (like ES) that is the same as a logstash configuration file. Parse and alter if you must, but it may be more simple (and reduce lines of code) to not parse the file at all. I.e. the user is responsible for passing the correct ES endpoint, etc.

[jhftrifork]

We've discussed this here before. I agree with your suggested approach. Users want to interact with mesos-logstash in a similar way to Logstash.

However we wouldn't be able to just pass through a Logstash config file without alteration. Some current features are more dynamic, e.g. adding the Mesos slave ID to each log event.

[frankscholten]

What about having the config file generated by the scheduler and available on an endpoint? On task launch it can be downloaded by the Mesos fetcher just like the executor Jar and the logstash distribution.

[mwl]

Another thing… So I was thinking about using a template engine like Freemarker to generate Logstash configuration. Which is fairly easy. But then comes the resources, mainly ports.
If we give users the freedom to put whatever they want into the configuration, they will end up writing the same things in more places.

I see two solutions to giving users total freedom with a template logstash configuration:

1. Parse up the generated Logstash configuration and guess what resources are needed
2. Take all resources allocated to role that are offered by Mesos.

I vote for 2nd.

[mwl]

Quite a few things happened here.

• The framework was migrated to Mesos-Starter
• Spring Boot got upgraded to 1.3.2
• Upgraded Minimisos to 0.6.something
• Implemented external configuration

[philwinder]

Probably not necessary considering the await next.

[mwl]

The driver throws a stupid Exception, because nothing was ready.

[philwinder]

That looks great Martin. Ready.

[philwinder]

Make sure you do some manual testing before you release, though.