Centralized logging solution on Mesos using ELK stack Imran Shaikh Lead Systems Engineer YellowPages
Issues? • No consolidated view – The problem gets worse if you are running multiple instances of an app. • How do you debug the issue? – Which container has the problem? • Lets say you are able to identify the container and there is nothing on STDOUT/STDERR: – how would you know its an issue with system, docker or mesos? – How do you stitch al this information together? • Lets say you are able to stitch it together: – how do you know which mesos task and marathon app this container belongs to? • There are multiple docker logging solutions, but none of the truly fits Mesos landscape.
Mesos so S s la S v la e v Dock D e ock r Cont Con a t iner 1 Dock D e ock r Cont Con a t iner 2 Dock oc e k r rCont Con a t i a ner rn Sy S s y t s e t m e logs YP Y Log L spou o t tCont Con a t i a ner Me M sos logs Sy S s y log Dock D e ock r rlog o s Log o st s a t sh h fo f r o wa w r a d r er rCont Con a t i a ner Mes e os DN D S N Logst s a t s a h Clu Cl s u t s e t r e Log o st s a t sh h 1 Logst s a t s a h 2 Logst s a t s a h 3 Logst s a t s a h n Ela El s a ti s cSe cS ar a c r h c Clu Cl s u t s e t r e ES E 1 ES E 2 ES E S 3 ES E n Ki K ban a a a Cont Con a t i a ner r1 Ki K ban a a Cont Con a t iner 2 Ki K ban a a Con C t on a t ine n r 3
What are we doing at YP Engineering? • Writing bunch of Mesos supported technologies: – Logging – Dynamically provisioning Application Secrets to containers – Persistent storage – Distributed Monitoring & Alerting – Metrics – Self-serve – Etc.
• Open source contribution: www.github.com/yp-engineering • You can reach us at: IRC: chat.freenode.net (#yp-engineering) Twitter: @imranshaikh Email: email@example.com, firstname.lastname@example.org • Any questions? We have a big contingent of a team here.