# ELK stack running on Marathon **URL:** \ **Category:** Elasticsearch\ **Created:** [September 24, 2015, 5:03pm UTC](https://discuss.elastic.co/t/elk-stack-running-on-marathon/29929 "2015-09-24T17:03:05Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [September 24, 2015, 5:17pm UTC](https://discuss.elastic.co/t/elk-stack-running-on-marathon/29929/2 "2015-09-24T17:17:09Z")
As it happens I just wrote a few paragraphs about Logstash and "high availability": > [@How to make Logstash highly available](http://discuss.elastic.co/t/how-to-make-logstash-highly-available/29926): > > Hi Experts, My plan is to make LS highly available as I did it for ES and Kibana. So I have load balancer for ES and for Kibana. Not sure how I achieve this for LS. Please suggest. Thanks VG > For Elasticsearch HA comes by default, but for Logstash and Kibana we didn't realize and easy way to make it (yes we can use Linux OS Cluster approach), but project see that approach as no flexible Kibana persists all state in Elasticsearch so you can just run it on multiple machines behind a load balancer. Kibana 4 basically just acts as a proxy to Elasticsearch so it's very lean on resources. Most of your other questions are probably more Marathon questions than they are ELK questions. Logstash and Kibana can be viewed as pretty generic TCP (and possibly UDP) based services. --- _[View the full topic](https://discuss.elastic.co/t/elk-stack-running-on-marathon/29929)._