Monitoring your application production errors

Today we have a lot of tools to improve your daily work and get your software ready for production.

But when we deploy how do we know if our users are having a great time using our application? How do we catch bugs?

Expecting them to send a bad review? cancel subscriptions? Or worse, they don’t complain about what they didn’t like, and you wait for your brand to end up getting a bad reputation?

I think that we need to anticipate that kind of thing, before our users complain about it, but how we can do that?

One of the ways is monitoring exceptions in production and fixing them as soon as possible.

In my point of view, every software in production that your company cares about should be monitored.

There is plenty of tools for monitoring and those tools catch requests info, the user logged, where the exception occurred and more.

Most of the tools have some free-plan in case your app is only getting started and you don’t have the money to pay for that.

The most popular tools have some sort of integration with frameworks like: Laravel, Symfony, React-native…

I already have used tools like bugsnag and sentry. But how I said, there is a lot of them.

So it’s your duty as a developer to pay attention to this kind of thing and improve the user experience with your software.