Look at improving DB + index structure for SentryIssue table
A discussion started in !22727 (comment 270849403) about the data integrity of SentryIssue
.
Background
A SentryIssue's sentry_issue_identifier
is only unique for a single Sentry instance.
We have behaviour where we find a SentryIssue via a sentry_issue_identifier
.
The problem with this is that there is a slight chance of having two SentryIssue records for a single project with duplicate sentry_issue_identifier
. This could happen if the user integrates with a Sentry instance + creates a Sentry Issue and then does the same with a second Sentry instance which generates a sentry_issue_identifier
the same as the first.
Possible Solutions
if we really want to be sure that we're finding the correct
SentryIssue
for asentry_issue_identifier
then I propose we also addproject_error_tracking_settings_id
to thesentry_issues
table.This will allow us to:
- Have proper uniqueness constraints for the
sentry_issue_identifier
- Easily allow us to find the correct SentryIssue for a given
sentry_issue_identifier
~"group::health" devopsmonitor backend database