Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Behind the Scenes at Coolblue - Feb 2017

485 views

Published on

In this talk, Pat stepped us through how we integrate with the #elasticstack here at Coolblue, using tooling like #Log4Net, #Serilog, #Seq and #Redis. Along the way, we were introduced to the role of each of these technologies, and as an added bonus, Pat demo'd how we can set some of these tools up in Docker containers in order to aid our rapid development and testing feedback cycles.

Published in: Technology
  • Be the first to comment

Behind the Scenes at Coolblue - Feb 2017

  1. 1. Behind the Scenes - Feb 2017 Pat Hermens p.hermens@coolblue.nl
  2. 2. All the things.
  3. 3. kibana elasticsearch beats logstash Elastic Stack.
  4. 4. 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
  5. 5. 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!
  6. 6. 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!)
  7. 7. 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
  8. 8. ● What is it/what was the predecessor? ● When was it first released? ● Why do we use it? Log4Net.
  9. 9. Other handy tools. “structured log visualiser” “in-memory data store”
  10. 10. More tooling.
  11. 11. “Seq is the fastest way for development teams to carry the benefits of structured logging from development through to production.” More tooling.
  12. 12. + More tooling.
  13. 13. Nightmares.
  14. 14. SMTPAppender.
  15. 15. PatsCustomAppender.
  16. 16. + More tooling.
  17. 17. + More tooling. +
  18. 18. So much tooling.
  19. 19. So much tooling.
  20. 20. In Production.
  21. 21. For our demo.
  22. 22. Nightmares.
  23. 23. Nightmares.
  24. 24. Monitoring.
  25. 25. Yes, monitoring.
  26. 26. Disclaimer.
  27. 27. The shiniest.
  28. 28. All the new things.
  29. 29. Conclusions.
  30. 30. Conclusions.
  31. 31. Conclusions.
  32. 32. Conclusions.
  33. 33. Conclusions.
  34. 34. ● 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.
  35. 35. Behind the Scenes - Feb 2017 Pat Hermens p.hermens@coolblue.nl

×