What Should You Log?

3min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

I'm half excited to do this episode just so I can do a little bit of improving on mine because maybe we should talk about that specifically like how do we log right now. through my template and it's funny this just how much logs can both pollute and save your bacon sometimes you know sometimes if there's too much logging too much noise you can't hear over certain things but part of what is good about having logging is that you can often go ahead and poth through the logs in a more structured and organized way. So too much information isn't necessarily a problem so what should you log here I'm going to tell you what we log and then we can maybe talk a

In this Hasty Treat, Scott and Wes talk about the reasons why you should log errors, how it’s not just for debugging, where to save logs, and apps and packages to help with logging.

Sentry - Sponsor

If you want to know what’s happening with your code, track errors and monitor performance with Sentry. Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up.

Show Notes