Change Details

There are several groups to whom a WMF-hosted or self-hosted Sentry instance could be interesting: * Labs tool maintainers could use the beta Sentry instance to log errors. This works for web services as well as bots run on Labs (or your own machine, for that matter) * People writing javascript code for the WMF production cluster (either as MediaWiki modules or gadgets/site scripts) can use `mw.errorLogging` to handle errors better (while errors would be reported anyway, manual error reporting can be used to add extra information or improve UX) * owners of 3rd party wikis can use Sentry to easily collect PHP + JS errors * may be useful for mobile apps / desktop tools? I'll hold a short presentation/demo about Sentry, then those who are interested can stay for a hacking session. I expect the presentation part will be ~15 mins.

[[https://getsentry.com/welcome/|Sentry]] is a tool to collect and aggregate errors. Any kind of error (PHP, Javascript, Python...) can be sent to the Sentry server, and it will display stats and provide rich information about the errors ([[http://sentry-beta.wmflabs.org/jserrors/jserrors/group/15/|example error page]]). There are several groups to whom a WMF-hosted or self-hosted Sentry instance could be interesting: * Labs tool maintainers could use the beta Sentry instance to log errors. This works for web services as well as bots run on Labs (or your own machine, for that matter) * People writing javascript code for the WMF production cluster (either as MediaWiki modules or gadgets/site scripts) can use `mw.errorLogging` to handle errors better (while errors would be reported anyway, manual error reporting can be used to add extra information or improve UX) * owners of 3rd party wikis can use Sentry to easily collect PHP + JS errors * may be useful for mobile apps / desktop tools? I'll hold a short presentation/demo about Sentry, then those who are interested can stay for a hacking session. I expect the presentation part will be ~15 mins.

[[https://getsentry.com/welcome/|Sentry]] is a tool to collect and aggregate errors. Any kind of error (PHP, Javascript, Python...) can be sent to the Sentry server, and it will display stats and provide rich information about the errors ([[http://sentry-beta.wmflabs.org/jserrors/jserrors/group/15/|example error page]]). There are several groups to whom a WMF-hosted or self-hosted Sentry instance could be interesting: * Labs tool maintainers could use the beta Sentry instance to log errors. This works for web services as well as bots run on Labs (or your own machine, for that matter) * People writing javascript code for the WMF production cluster (either as MediaWiki modules or gadgets/site scripts) can use `mw.errorLogging` to handle errors better (while errors would be reported anyway, manual error reporting can be used to add extra information or improve UX) * owners of 3rd party wikis can use Sentry to easily collect PHP + JS errors * may be useful for mobile apps / desktop tools? I'll hold a short presentation/demo about Sentry, then those who are interested can stay for a hacking session. I expect the presentation part will be ~15 mins.