logstash

We are using CoreOS for the host servers, dumping logs to logstash, and connect the containers via HAProxy.

It can monitor Logstash and Graphite, which are proven ways to collect data in a disparate environment.

You can also use logstash to generate metrics on logs when sending them up to Elasticsearch.

Contact me if you need anything around the ELK stack - Elasticsearch, Logstash or Kibana.

I'm a big fan of elastic search, but don't have any exposure to logstash or kibana.

As far as logs go, you should just be doing network logging with Docker to either a syslog server or something like LogStash or Splunk.

Nginx and Apache ELK stack - Elasticsearch + Logstash + Kibana.

As for LogStash & ES: Guess what: their storage is binary.

Honestly - I agree about the ELK stack side - piping all your logs into ES / Logstash is a great idea.

Think Riemann, Sensu, Statsd, Logstash (Indexers + Elasticsearch Cluster).

Instead, if you have text files being written out, and something like beaver collecting them and sending them to logstash, you have the best of both worlds.

We've been using kibana setup with logstash for allowing us to easily track things we want to track/graph for a project I'm working on.

Logstash, Splunk and other tools store stuff binary, as he writes, and that's perfectly valid, the only solution in fact.

ELK stack - Elasticsearch, Logstash, and Kibana.

We are hosting our own EHK (Heka instead of Logstash) stack for ~$50/mo (few hours of setup and ~10mins/month of maintenance) which would cost us about $500/mo if we would have stayed with Loggly (and ours will stay at about the same price well into the volume of Loggly's $1k/mo plan).