This document discusses various tools in the Elastic Stack including Kibana, Elasticsearch, Beats, and Logstash. It provides brief descriptions of each tool and why they are used. Additional logging and monitoring tools are also mentioned, along with links to documentation, code samples, and other resources from the discussion.

1. Behind the Scenes - Feb 2017
Pat Hermens p.hermens@coolblue.nl

4. All the things.

5. kibana
elasticsearch
beats logstash
Elastic Stack.

6. Elastic Stack.
Kibana
● “A visualisation tool that ties into Elastic Search”
● Why do we use it?
○ It “just works” with the rest of the stack
○ Visualisations and dashboards are “good enough” and getting better

7. Elastic Stack.
Elastic Search
● “A performant search engine & data store”
● Why do we use it?
○ Great at storing large amounts of data, and
○ Fantastic at searching through it!

8. Elastic Stack.
Beats
● “It ships logs so you don’t have to”
● Why do we use it?
○ Lots of machines
○ Lots of environments
○ Lots of moving parts
○ Lots of legacy that we need to support (Thanks FileBeats!)

9. Elastic Stack.
Logstash
● “The entry-point into the Elastic Stack”
● Why do we use it?
○ It splits up each log into a separate index
○ It enriches logs...
■ e.g.: Given an IP address, it can add city and country
■ e.g.: Given a server name, it can add environment name
■ HINT: Given a structured string, it can break it apart

10. ● What is it/what was the predecessor?
● When was it first released?
● Why do we use it?
Log4Net.

11. Other handy tools.
“structured log visualiser” “in-memory data store”

13. More tooling.

14. “Seq is the fastest way for development teams
to carry the benefits of structured logging
from development through to production.”
More tooling.

15. +
More tooling.

19. Nightmares.

20. SMTPAppender.

22. PatsCustomAppender.

24. +
More tooling.

26. +
More tooling.
+

27. So much tooling.

28. So much tooling.

29. In Production.

30. For our demo.

32. Nightmares.

33. Nightmares.

35. Monitoring.

36. Yes, monitoring.

37. Disclaimer.

39. The shiniest.

40. All the new things.

41. Conclusions.

42. Conclusions.

43. Conclusions.

44. Conclusions.

45. Conclusions.

46. ● Documentation & code from tonight:
○ https://github.com/phermens-coolblue/bts-2017-february/
● Seq running on a Windows Server Core image:
○ https://github.com/phermens-coolblue/bts-2017-february/tree/master/docker/seq
○ ...or https://hub.docker.com/r/pheonix25/servercore-seq/
● ELK & Redis running on Docker:
○ https://github.com/phermens-coolblue/bts-2017-february/tree/master/docker/elk
● Coolblue DevBlog:
○ http://devblog.coolblue.nl/
● Slides (and possibly video) will be available soon:
○ @phermens, or https://hermens.com.au
Links.

48. Behind the Scenes - Feb 2017
Pat Hermens p.hermens@coolblue.nl