Change Details

Sentry was installed in 2016 as Docker containers. Notifications Center uses it to report exceptions, and there are plans for: - Zed: report exceptions (old code with Raven lib proof of concept to modernize) - Auth Grove: same configuration than Notifications Center (but see T1771 moratoire on Auth Grove dev) - Wearg / Dæghrefn: check for new errorInfo content (see T1790) It's especially important for Wearg, Dæghrefn and Notifications Center as humans don't have access to the errors when it's automatically processed. We've some Gb of data of repeating errors from Notifications Center in pgsql, a db schema not compatible with 9.1.2 version (the stop before switching to CalVer). Interest of those are dubious, as Dorian updated the code to modern Laravel, and as I've hunted and solved Notifications Center / Phabricator main issues. Meanwhile, Sentry codebase evolved. The old image seems to be stucked to 9.1.2 3 years ago Instead of upgrading, I suggest to reinstall it from scratch, especially as we don't have any used history or applications reporting.

Sentry was installed in 2016 as Docker containers. Notifications Center uses it to report exceptions, and there are plans for: - Zed: report exceptions (old code with Raven lib proof of concept to modernize) - Auth Grove: same configuration than Notifications Center (but see T1771 moratoire on Auth Grove dev) - Wearg / Dæghrefn: check for new errorInfo content (see T1790) It's especially important for Wearg, Dæghrefn and Notifications Center as humans don't have access to the errors when it's automatically processed. We've some Gb of data of repeating errors from Notifications Center in pgsql, a db schema not compatible with 9.1.2 version (the stop before switching to CalVer). Interest of those are dubious, as Dorian updated the code to modern Laravel, and as I've hunted and solved Notifications Center / Phabricator main issues. Meanwhile, Sentry codebase evolved. The old image seems to be stucked to 9.1.2 3 years ago Instead of upgrading, I suggest to reinstall it from scratch, especially as we don't have any used history or applications reporting. Then setup reporting for the applications needing this service the most.

Sentry was installed in 2016 as Docker containers. Notifications Center uses it to report exceptions, and there are plans for: - Zed: report exceptions (old code with Raven lib proof of concept to modernize) - Auth Grove: same configuration than Notifications Center (but see T1771 moratoire on Auth Grove dev) - Wearg / Dæghrefn: check for new errorInfo content (see T1790) It's especially important for Wearg, Dæghrefn and Notifications Center as humans don't have access to the errors when it's automatically processed. We've some Gb of data of repeating errors from Notifications Center in pgsql, a db schema not compatible with 9.1.2 version (the stop before switching to CalVer). Interest of those are dubious, as Dorian updated the code to modern Laravel, and as I've hunted and solved Notifications Center / Phabricator main issues. Meanwhile, Sentry codebase evolved. The old image seems to be stucked to 9.1.2 3 years ago Instead of upgrading, I suggest to reinstall it from scratch, especially as we don't have any used history or applications reporting. Then setup reporting for the applications needing this service the most.