How to ditch the debugger and use logging instead - devwinter 2015
•
6 j'aime•2,359 vues
As a Developer, you cannot attach the debugger to your application in Production, but you *can* use logging in a way which means you can diagnose problems very easily in both development AND Production. You also get to make friends with Operations people - win! In this tutorial, we'll show you how to get up and running with ELK (Elastic Search, LogStash, Kibana) with Vagrant on your developer machine for awesome logging-fu. Warning: may contain DevOps.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à How to ditch the debugger and use logging instead - devwinter 2015
Similaire à How to ditch the debugger and use logging instead - devwinter 2015 (20)
Plus de Skelton Thatcher Consulting Ltd
Plus de Skelton Thatcher Consulting Ltd (20)
Dernier
Dernier (20)
How to ditch the debugger and use logging instead - devwinter 2015
- 1. How to ditch the debugger and use logging instead Matthew Skelton & Rob Thatcher, Skelton Thatcher Consulting /dev/winter 2015, Saturday 24th January, Cambridge, UK #devwinter
- 2. Event tracing Vagrant + ELK Demo: no debugging
- 3. Skelton Thatcher Introduction and Services Overview
- 4. ‘Cloud’ changes the way we must design, deliver, and operate our software systems
- 7. Event type IDs Transaction tracing Adjusting logging levels
- 8. Event type IDs How many event types in your application?
- 10. Event type IDs enum Human-readable sets: unique values, sparse, immutable C#, Java, Python, node (Ruby, PHP, …)
- 11. public enum EventID { // Badly-initialised logging data NotSet = 0, // An unrecognised event has occurred UnexpectedError = 10000, ApplicationStarted = 20000, ApplicationShutdownNoticeReceived = 20001, PageGenerationStarted = 30000, PageGenerationCompleted = 30001, MessageQueued = 40000, MessagePeeked = 40001, ItemAddedToBasket = 60001, ItemRemovedFromBasket = 60002, CreditCardDetailsSubmitted = 70001, // ... }
- 12. Technical Domain public enum EventID { // Badly-initialised logging data NotSet = 0, // An unrecognised event has occurred UnexpectedError = 10000, ApplicationStarted = 20000, ApplicationShutdownNoticeReceived = 20001, PageGenerationStarted = 30000, PageGenerationCompleted = 30001, MessageQueued = 40000, MessagePeeked = 40001, ItemAddedToBasket = 60001, ItemRemovedFromBasket = 60002, CreditCardDetailsSubmitted = 70001, // ... }
- 17. Monolith to microservices: debugger does not have the full view Distributed systems
- 18. Even with remote debugger, it’s boring to attach and detach Remote debugging?
- 20. Transaction tracing Unique-ish identifier assigned to web request Passed through downstream layers
- 21. What about APM? APM gives us application insight BUT How much do we learn? Is APM available on the Dev box? It’s not just ‘an Ops problem’!
- 22. Minimal viable tracing? Helps us to understand how the software really works Small overhead is worth it
- 23. Which log level is right? DEBUG, INFO, WARNING, ERROR, CRITICAL
- 24. Which log level is right? Log level should *not* be fixed at compile or build time!
- 25. <?xml version="1.0" encoding="utf-8" ?> <Application.EventMappings> <Events> <Event Type="CacheServiceStarted"> <Severity Type="Information"/> </Event> <Event Type="PageCachePurged"> <Severity Type="Debug"/> <Enabled="false"/> </Event> <Event Type="DatabaseConnectionTimeOut"> <Severity Type="Error"/> </Event> </Events> </Application.EventMappings>
- 26. Tune log levels
- 27. Tune log levels
- 28. Tune log levels
- 30. Dev and Ops collaboration* * and testers too!
- 32. Event tracing Use enumerations (or closest thing) Technical and Domain event types Distributed systems: debuggers less useful Trace calls with ‘unique-enough’ handles Tune log levels via config
- 33. Vagrant + ELK
- 34. Log Aggregation Elasticsearch, Logstash & Kibana Vagrant
- 35. Log Aggregation
- 36. Multiple log sources Many logs in one place Searchable Time Sequenced
- 43. Vagrant
- 44. Ruby CLI to deploy Virtual environments Deploy locally to AWS or Azure etc.
- 45. Four Simple Steps $ vagrant box add ubuntu/trusty64 $ vagrant init trusty64 $ vagrant up $ vagrant ssh
- 47. • Listening to: • Local nginx logs • Local Syslog • (Application logs) http://bit.ly/velk-demo Vagrant + ELK Demo VM
- 54. Recap
- 55. Aggregated Logging: Vagrant + ELK Centralised logs, time sequenced, searchable Vagrant :quickly spin up & manage machines ELK : collect, store, display & search logs Developer-friendly!
- 56. Demo: ditching the debugger
- 57. Vagrant on developer laptop ELK for log aggregation Web app: PHP (Slim) Event type IDs Demo: background
- 58. Use VirtualBox shared folders Browse to Kibana UI via NAT-ed interface
- 59. Event type IDs Log aggregation with ELK Demo
- 79. Demo: summary Super-easy to hook application logs into ELK Sequences of events emerge Compare timings of events: past and present
- 80. Recapitulation
- 81. How to ditch the debugger Use Vagrant + ELK on development VM Use a set of event type IDs (enums) Log distinct states of execution Both technical and domain events Consistent event naming helps with search Compare previous and current executions New logging-fu: make friends with Ops!
- 82. Links Tune logging levels in Production without recompiling code: http://bit.ly/TuneLoggingLevels VELK (Vagrant + ELK) demo VM: http://bit.ly/velk-demo GOOS book (section on logging: p.233-5): http://www.growing-object-oriented-software.com/