The document discusses tools for debugging production applications, including airbrake_tools and air_man for monitoring exceptions, request_recorder for tracking HTTP requests and logs, and ultragrep for searching and analyzing logs, and it emphasizes the importance of understanding exceptions, logs, and reproducing issues before deploying fixes. It also mentions that the author is hiring for Ruby, Ember, and DevOps roles in San Francisco.

1. Debugging
Production

2. @grosser grosser.it github.com/grosser
Michael Grosser
Ruby/Rails Framework Engineer

4. Exceptions
Logs
Reproduction

5. Exceptions:
In the beginning they are
helpful in the end they are
noise.

7. airbrake_tools

8. Hot

9. List

10. Summary

12. air_man
github.com / grosser / air_man

15. ✓Exceptions
Logs
Reproduction

16. request_recorder
github.com / grosser / request_recorder

20. ultragrep
github.com / zendesk / ultragrep

21. - log folder structure <server>/year/month/day
- 1 log per day 00:00 - 23:59
- 2 newlines between requests

22. ✓Exceptions
✓Logs
Reproduction

23. Login as customer:
- master password
- admins can log in as end-user
- log who auths as whom

24. validate fix in production
before deploying

25. - prefer read only server
- app.get / post
- helper.link_to

29. ✓Exceptions
✓Logs
✓ Reproduction

30. Know your exceptions
- hot / patterns (airbrake_tools)
- monitor (air_man)
- track http status codes

31. Know your logs
- redirects / queries
(request_recorder)
- search / info / data (ultragrep)

32. Reproduce to debug
Reproduce before deploying

33. Also hiring (Ruby/Ember/DevOps/...) -> live in sunny SF ;)