Imagine your website suddenly runs slow from one minute to the other. You have done no code updates, no server updates and you can not see any errors in the logs. The first thing you do is call your host to ask them what is going on.

After some time and a lots of dead ends, you ask them for information about load, visits, and visitors. But you don't get them and you have no access to their data but you do to the apache logs.

This talk is about how i was able to get the dat ai wanted using Docker and elk to see what IP addresses were hitting the servers harder than they should and all the other data i could acquire by downloading and importing the acces logs and some handy filters without having to create an elk stack of my own.


Comments are closed.

Boy Baukema at 14:30 on 1 Jul 2017

Content was very interesting! Melvin spoke well and down to earth, you could tell he had practical experience with this that he was sharing insight into something that is very applicable to just about every developer: troubleshooting performance issues in a hurry with ELK and Docker.
This talk was limited by 2 things: not enough seats! Very popular talk. And not enough preparation, which is fine for an uncon but I hope he gets the chance to speak as a speaker and fully work out this talk.

Disclaimer: I used to work with Melvin

Sander vT at 15:01 on 1 Jul 2017

A beginner level talk. I hoped for more best practices or lessons learned on running ELK on a high traffic website.
Spend some more time on your slides next time.

Deniz Zoeteman at 20:53 on 1 Jul 2017

An interesting practical example of using ELK stack. For future talks, if a demo doesn't work, I'd just skip instead of trying to fix it, as you lose the audience a little then.

Nice introduction to the ELK stacker and how you solved your problem! The live demo gave you some issues in the beginning but was really adding a lot of value to the talk.
My advice for a future talk is to be more prepared, especially if you give a live demo. You can perfectly save the configuration of the graphs somewhere so the audience doesn't have to wait that long.

Max Roeleveld at 16:06 on 2 Jul 2017

Interesting, content-wise, and a somewhat novel way / reason to use ELK. As others have pointed out, preparing a talk like this a bit more might keep the tempo up.