As teams build and compose more services, their dependency on logging grows exponentially. Being able to quickly make use make use of those logs can easily mean the difference between quickly finding a bug and struggling to even understand it for weeks. For this reason, services that make their logging data easy to consume by tools result in "higher order logs", allowing the logs to be usable data rather than just walls of text.
In this talk, we'll go over:
* Why you should use structured logs
* How to add structured logs to ruby services
* What you should log in the first place!
* Tools and workflows to make use of those structured logs