Hi, here is a comment on a 6 years-old task :)
Having Sentry instance on labs for tools and websites is a long dream for me, that would these days more than ever be useful for lot of people.
I have been trying in recent days to set up a test instance, and use it with Quarry real-data. Found lot of things to fix with this :)

@Tgr and @akosiaris , on T91649#5700798 you provided very usefull note regarding Sentry license. It is then clear that Sentry will not be deployed on production wikis.
However, i'm not sure about the licensing issues that may be raised for a deployment on wmcloud, with cloud/tools as end-users. I.e. labs ToS says Do not use or install any software unless the software is licensed under an Open Source license.

Can you help me clarify this point? I'd like to get a clearer picture before I go any further. If license is not compatible with wmcloud, we can close this task then.

@Framawiki: See "All Approved Licenses" on https://opensource.org/licenses/ and compare to https://github.com/getsentry/sentry/blob/master/LICENSE , basically.

@Framawiki, sure. https://github.com/getsentry/sentry/blob/master/LICENSE is pretty clear:

The Business Source License (this document, or the "License") is not an Open
Source license. However, the Licensed Work will eventually be made available
under an Open Source License, as stated in this License.

As such, if one would install sentry as is in WMCS, they would be violating #3 of the the prohibited uses. The exception being in this very specific case that if they waited out the 3 years after the release of the version they want to install that would be ok since after 3 years the software is re-released under the Apache 2 license. However that would mean an already 3 year old and possibly unsupported software (despite my efforts, it's unclear to me if they would be releasing e.g. security patches for 3 year old releases). Whether that risk is acceptable or not is up to them and should be a conscious and deliberated upon decision.

Per T262931: Set up an exception logging service some WMF teams use GlitchTip so probably the first thing should be to check if that could be an acceptable replacement for the Quarry use case.

I have marked the WMCS project for deletion; with Sentry not being FLOSS anymore it's unlikely to move forward. We could set up a GlitchTip project instead - it's a FLOSS reimplementation of the Sentry backend, seems less capable, but it's API compatible. (The current Sentry WMCS install is still FLOSS so feel free to mark the project for keeping if you disagree.)