SponsorsAudible - get a free audiobook from Audible with no strings attached at https://workingcode.dev/audibleUnder the right circumstances, application and error logs can be magical. They can shed light on how a system is behaving - or misbehaving; and, they can provide a path forward in an emergency situation. But, logs do come at a cost. Not only is there an actual dollars-and-cents cost to aggregating and storing logs, having too many logs can end-up reducing the signal-to-noise ratio which can make it harder to debug a running application.This week on the show, the crew talks about different categories of logging, why some logging is required for regulatory purposes, how you can replace certain logs with telemetry and metrics, and why you should absolutely never ever email yourself errors... except for when you should; because it's easy; and because we never learn from our mistakes.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.