I would probably recommend using the existing EventLogging infrastructure
for sending the data to our back end, assuming it won't explode under heavy
load spikes... Which it might. :)
Eventlogging is not the best choice. Besides
not handling bursts of traffic it is -currently- a tier-2
2014-07-25 1:13 GMT+03:00 Gergo Tisza gti...@wikimedia.org:
Many sites solve this issue by setting up an error handler in Javascript
which reports any errors that occurred to a logging server. I tried to make
a laundry list of things that need to be done or considered if we want to
set up
Hi all,
frontend development is greatly hindered by not having logs of errors that
happen in production. If there is a mistake in a PHP file, it is usually
quickly caught after deployment when a large number of exceptions show up
in the error log. If the mistake is in a JS file, it can take a
I would probably recommend using the existing EventLogging infrastructure
for sending the data to our back end, assuming it won't explode under heavy
load spikes... Which it might. :)
-- Brion
On Jul 24, 2014 3:14 PM, Gergo Tisza gti...@wikimedia.org wrote:
Hi all,
frontend development is
