Handling Unique Constraint for Reverted Events

[NikolasHaimerl]

Context

After the hotfix that deals with unique constraints when inserting active deals, the reverted field is currently being ignored in unique constraints. This raises the question of how to handle unique constraints while considering reverted events.

Proposed Solutions

1. Delete the unique constraint
2. Keep the unique constraint and assume that reverted events don’t trigger it
3. Keep the unique constraint and handle reverted events separately
4. Remove the reverted field from the database and handle reverted events separately
5. Keep the unique constraint and the reverted field and send information about reverted events directly to telemetry

Agreed Approach

We will add information about reverted events directly to telemetry while inserting new active deals**. This allows us to continue monitoring reverted events without interfering with the unique constraint.

Subtasks

• Modify deal insertion logic to send reverted events information directly to telemetry.
• Update Grafana dashboards to track reverted events via telemetry instead of the database.