Back

Error reporting on or off for production?

  • 0
  • General
  • Flutter
alza
10 Jul, 2023, 17:25

Hey everyone, I'm about to start working with Appwrite for my Flutter app and i was looking through the documentation for the self-hosted version. In this it says:

`Error Reporting

By default, your Appwrite installation comes with error reporting turned off. You can turn it on in dev mode to try and debug issues or report problems.

In production, it is highly recommended to turn error reporting off. To do so, make sure the Appwrite container environment variable _APP_ENV is set to production and not development.`

Can someone elaborate to why the recommendation is to turning off the reporting for production?

TL;DR
The recommendation is to turn off error reporting for production because logging errors can add a few milliseconds to overall request time. It is not due to security concerns. However, during the MVP phase and for a short time after, it can be beneficial to keep error reporting on to log bugs and build a more stable product. To turn off error reporting in Appwrite's self-hosted version, set the Appwrite container environment variable _APP_ENV to production.
Binyamin
10 Jul, 2023, 17:33

Hey,

I think it's due to the simple fact that every logging will add a few milliseconds to your overall request.

I don't think is from security reasons, as if someone gained access to the server that would be the least of your worries..

alza
10 Jul, 2023, 20:20

Ahhh okey, that makes a lot of sense. So then it could still be a good choice to keep it on during the MVP and perhaps a short time after, just to make sure to log bugs and be able to build a more stable, mature product.

thanks @Binyamin

Binyamin
10 Jul, 2023, 20:53

Imo, yes.

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more