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.

SplunkLive! Utrecht 2017 - Coolblue Customer Presentation

458 views

Published on

Coolblue's customer slides from SplunkLive! Utrecht 2017, presented by Matthew Hodgkins, Technical Pathfinder.

Attendees of SplunkLive! Utrecht learnt how more than 14,000 enterprises, government agencies, universities and service providers in over 110 countries use Splunk software to deepen business and customer understanding, mitigate cybersecurity risk, prevent fraud, improve service performance and reduce cost.

Published in: Technology
  • Be the first to comment

SplunkLive! Utrecht 2017 - Coolblue Customer Presentation

  1. 1. Matthew Hodgkins | SplunkLive! Utrecht
  2. 2. A Little About Me ● Been at Coolblue 1.5 years ● Background in operations ● Focus is monitoring and logging
  3. 3. Disappointment
  4. 4. Whoops
  5. 5. Agenda ● A little about Coolblue ● Logging in Coolblue before Splunk ● The migration to Splunk ● The benefits we found after moving
  6. 6. Business plan
  7. 7. Picture from last hackathon
  8. 8. Picture from last hackathon
  9. 9. ELK Architecture
  10. 10. Easy right? # For e-commerce send logs here 10.0.0.2:6379
  11. 11. Challenges ● Around 180 Developers ● Many Languages ○ C# ○ PHP ○ Python ○ Node.JS ○ Delphi
  12. 12. ELK Architecture
  13. 13. Challenges # For e-commerce send logs here 10.0.0.2:6379 # For backoffice send logs here 10.0.10.2:6379
  14. 14. Challenges ● Logs everywhere ○ Windows / Linux / Network Devices ○ Logging to disk ○ No standardization
  15. 15. Offices
  16. 16. ELK Architecture
  17. 17. Physical stores
  18. 18. Warehouses
  19. 19. ELK Architecture
  20. 20. Challenges # For e-commerce send logs here 10.0.0.2:6379 # For backoffice send logs here 10.0.10.2:6379 # For amsterdam store send logs here 192.168.2.2:6379 # For rotterdam store send logs here 192.168.3.2:6379
  21. 21. Challenges ● Storage ● Retention
  22. 22. Microservices. Microservices Everywhere.
  23. 23. The main reasons ● Amazing AWS integrations (Splunk App for AWS)
  24. 24. The main reasons ● Amazing AWS integrations (Splunk App for AWS) ● Fully managed
  25. 25. The main reasons ● Amazing AWS integrations (Splunk App for AWS) ● Fully managed ● No more worrying about architecture changes with growth
  26. 26. The migration ● Standardized logging frameworks ● Log however you want, as long as its JSON ● Reviewed a ton of dashboards ● Planned a new architecture
  27. 27. The migration ● Standardized logging frameworks
  28. 28. The migration ● Standardized logging frameworks ● Log however you want, as long as its JSON
  29. 29. The migration ● Standardized logging frameworks ● Log however you want, as long as its JSON ● Reviewed a ton of dashboards
  30. 30. The migration ● Standardized logging frameworks ● Log however you want, as long as its JSON ● Reviewed a ton of dashboards ● Planned a new architecture
  31. 31. Splunk Cloud Architecture
  32. 32. Splunk Cloud Architecture - AWS
  33. 33. Splunk Cloud Architecture - On Premise
  34. 34. So where are we now?
  35. 35. So where are we now?
  36. 36. Benefit - Easier Config ● Logging by convention # wherever you are, send logs here 127.0.0.1:514
  37. 37. Benefit - Easier To Test
  38. 38. Benefit - Exploration
  39. 39. Benefit - New apps are easy ● New service coming online? ○ Create an index for the service
  40. 40. Benefit - New apps are easy ● New service coming online? ○ Create an index for the service
  41. 41. Benefits - Templated dashboards ● Templated dashboards
  42. 42. Benefits - Real Time Dashboards ● Templated dashboards
  43. 43. Benefits - Audit Trails ● Templated dashboards
  44. 44. Benefits - Overall Health ● Templated dashboards
  45. 45. Benefits - Other Teams Onboard ● Templated dashboards
  46. 46. Benefits - Time Saved ● Templated dashboards
  47. 47. ● Know what’s important to you and your customers ● Make logging as simple as possible ● Dashboard templating Takeaways
  48. 48. ● m.hodgkins@coolblue.nl ● @MattHodge ● http://devblog.coolblue.nl ● http://careersatcoolblue.com

×