Improve exception handling
What does this MR do?
This is follow-up after gitlab-foss!23422 (closed).
This adds a new file: exceptions_json where we log all exceptions
that are by user-required to be trackable, via Gitlab::Sentry.
This also improves a naming of the methods, as they are confusing:
-
from
track_acceptable_exception=>track_exception: we just want to capture exception -
from
track_exception=>track_and_raise_for_dev_exception: as said, -
from
track_and_raise_exception=> we want to capture and re-raise
Closes: #32906 (closed).
Does this MR meet the acceptance criteria?
Conformity
Edited by 🤖 GitLab Bot 🤖