#On Logging and Smoothies
At Perka, we have a logging system called "Firehose" that integrates every HTTP envelope, API payload, event dispatch, database query, thrown exception, and console message into a unified dashboard. The dashboard has views for triaging production issues, allowing all records associated with a particular HTTP request to be displayed, and it also supports data-mining by writing JavaScript reduction scripts. Firehose has been a good experiment in determining what "useful logging" really means.
Useful logs should be:
- Comprehensive
- Correlated
- Clearly actionable