![]() And it's basically on every device which makes it easier to notice notifications when something bad is happening.Īnd with help of Slack channels I could send error logs to them for each of my projects. It's an application that I almost always have opened, maybe even more than my email. Why not use Slack? People are using it to order Uber, look at GIFs or play ping-pong. I needed something better but also similar in ease of installation, accessibility and price (free). And using server error logging to email was especially cumbersome when it came from multiple different projects. Recently I've started working on some additional Django projects deployed to production (one of them is ). But those are not always free and they require some setup and maintenance which in most cases is not worth it for smaller projects. Some use tools like Sentry or Rollbar and some even go with custom solutions. Such mess.Įvery developer (or team of developers) has its own methods for logging their server errors. It's not for error logs that make even more mess in your inbox – especially if you get a ton of them after you've introduced highly public facing bug in your last deployment. But lets agree – email is primarily for communication between humans and (of course) for incoming spam from email lists you don't even remember you've signed up for. It's pretty useful and better than nothing. If you develop small sized applications using Django framework then you most probably use Django built-in error logging via email. If you just want to jump to the final code click here. ![]() It might work on older versions but I haven't tried it. These packages and versions were used in this guide It's only meant as a replacement for Django standard email error reporting for small projects in initial stages where integrating full-blown error reporting service would be an overkill. This solution isn't meant as a replacement for Sentry, Bugsnag, Rollbar or anything similar.
0 Comments
Leave a Reply. |