Changelog

Version 3 - unreleased

☐ DCOS certification
☐ Loss-less logging. Thoroughly ensure that no log messages are lost. (e.g. when a container has rolling log files)
☐ Enhanced Error and Failover Handling
☐ Support for streaming output from docker log
☐ Support for arbitrary Logstash Plugins
☐ Service Discovery (allow frameworks to discover the log service automatically, and configure themselves)

Version 2 - 2015-08-14

☑ Basic Failover Handling with Zookeeper
☑ Allow reconfiguring running frameworks
☑ Basic DCOS compliance (Alpha stage)

The available DCOS configuration options are documented in DCOS config.json.
```
dcos config append package.sources "https://github.com/triforkse/universe/archive/version-1.x.zip"
dcos package update
dcos package install --options=logstash-options.json logstash
```
The logstash-options.json file in the above example is where you can configure Logstash with your own settings. Here is an example logstash-options.json.

Note: Uninstalling the logstash DCOS package will shutdown the framework! See Updating to new version how to preserve the your Logstash slave and docker configuations.

Version 1 - 2015-07-24

☑ Automatic discovery of running frameworks, streaming logs from files inside the containers. (This feature has since been removed.)
☑ Shared Test- and Development- Setup with mesos-elasticsearch, mesos-kibana
☑ External LogStash Configuration (config files propagated from Master to Slaves)
☑ Support for outputting to Elastic Search
☑ Basic Error Handling
☑ Installation Documentation
☑ Design Documentation
☑ Configuration GUI
☑ REST API for managing Configurations. Here is the spec:

/api/configs is a JSON array of configurations. A configuration is a JSON object with the schema:
```
{
    "name": string, // The name of the docker image to match when,
    "input": string // The Logstash configuration segment for this framework.
}
```
GET /api/configs returns the array of configurations.

POST /api/configs creates a new configuration for a framework. The new framework will be available at /api/configs/{name}.

/api/configs/{framework-name} is an existing framework config.

PUT /api/configs/{framework-name} updates an existing framework config. Make sure that framework-name is proper URL encoded (e.g. in JavaScript see encodeURIComponent).

DELETE /api/configs/{framework-name} removes the configuration for this framework. Make sure that framework-name is proper URL encoded (e.g. in JavaScript see encodeURIComponent).