Le 13/06/2019 14:20, Lester Caine a écrit :
On 13/06/2019 13:04, Andrey Andreev wrote:
You have logs to see the errors; relying on your users to report the
actual error messages to you is the worst way to do it.
How many website logs can you manage on a daily basis? Given the
volume of material in heavily used website. I am STILL trying to get
long established sites back to a state where that would be a practical
approach. Especially when adding material is first element on the
to-do list. I've several hours of such work to get cleared first and
prompts in that traffic is easier to manage than then working through
several machines worth of logs ...
Have you considered using solutions like Sentry?
https://sentry.io/welcome/
It gets added to the error handler and will report errors to a server.
Quite handy.
Another solution is to use the shutdown and error handler to send an
email to you when there is an error:
https://stackoverflow.com/questions/277224/how-do-i-catch-a-php-fatal-error
We used that solution for quite some time, but it can quickly overload
your email server when you have millions of requests producing errors ;)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
