Move Sentry Api caching out of `ProjectErrorTrackingSetting`
The following discussions from !22174 (merged) should be addressed:
-
@jprovaznik started a discussion: (+1 comment) Not directly related to this MR, but I wonder if
ProjectErrorTrackingSetting
model is a good fit for having business logic related to fetching Sentry data? It seems this model should take care of settings related logic only, fetching of sentry issues should be done separately (e.g. some Service class). This doesn't have to be addressed as part of this MR, but I'd like to clarify what is the plan with this class or if I missed something (I'm happy to create a follow-up issue for this).
Ideas
- Create a separate model responsible for caching the response from sentry and adding doing any post-processing on that data
- Cache the fetched sentry data within the existing Services that are called from the error tracking controller like the
ListIssuesService
.
Edited by 🤖 GitLab Bot 🤖