Thanks for the response.
I had taken a look at Sentry earlier and while it seemed great at first, it's primarily targeting errors. Trakerr helped me find performance issues with database issues too as you can pass in the milliseconds that a db call took along with other non-error logs. I haven't looked at Flask but will take a look.
I am actually surprised by the number of developers who do not use an error or performance tracking tool in production. Given that verbose logging is very prohibitive in terms of cost and performance, the only fallback to catching major issues in production appears to be using some real-time metrics + error capturing technology.
I had taken a look at Sentry earlier and while it seemed great at first, it's primarily targeting errors. Trakerr helped me find performance issues with database issues too as you can pass in the milliseconds that a db call took along with other non-error logs. I haven't looked at Flask but will take a look.
I am actually surprised by the number of developers who do not use an error or performance tracking tool in production. Given that verbose logging is very prohibitive in terms of cost and performance, the only fallback to catching major issues in production appears to be using some real-time metrics + error capturing technology.