Philipp Krenn

Philipp Krenn

Developer Advocate at Elastic, Austria

Philipp lives to demo interesting technology. Having worked as a web, infrastructure, and database engineer for more than ten years, Philipp is now working as a developer advocate at Elastic — the company behind the open source Elastic Stack consisting of Elasticsearch, Kibana, Beats, and Logstash. Based in Vienna, Austria, he is constantly traveling Europe and beyond to speak and discuss about open source software, search, databases, infrastructure, and security.

Speaker's activity

Live Kubernetes Debugging with the Elastic Stack

December 7th

10:00

Talk

English

Your Kubernetes app is down. Your users start ranting on Twitter. Your boss is standing right behind you. What do you do?

This talk walks you through a live debugging session without panicking:

* What do your health checks say?
* Where does your monitoring point you?
* Can you get more details from your application’s traces?
* Is there anything helpful in the logs?
* What the heck is even deployed?

We are using the open source Elastic Stack in this demo with a special focus on its Kubernetes integration with metadata enrichment and autodiscovery in combination with APM/tracing, metrics, logs, and health checks.

Official Docker Images - Lessons Learned

December 8th

12:10

Talk

English

If you want to be taken seriously, you need to provide containers to your users. It’s easy — everybody is uploading containers to Docker Hub, right? Unfortunately, reality is never as easy as it sounds at first. This talk gives an overview of Elastic’s ongoing journey to providing official Docker images:

* Docker Hub: What “official” really means and why we are using our own registry.
* Base image: Just use Alpine — it is small and the perfect fit for containers. We tried that and reconsidered…
* Release policy: What do you actually get in a specific tag and how are we releasing our images?
* Support: Combine two complex systems like Elasticsearch and Docker — and you will get a lot of questions.
* Orchestration: Our current approach for orchestration and how we are treating feature requests.