getsentry / getsentry/sentry

Delete UserReports after retention

Open
#89,964 1 comment 0 reactions 0 assignees View on GitHub
Improvement Product Area: User Feedback
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

The UserReport postgres model is used for backwards compatibility w/older user feedback sources, and also to associate feedback to groups (issues). A user report is only valid if its associated `event_id` + `group_id` exists in the same project.

Therefore to save COGS, we can delete reports after the max event retention (90d(?)). Maybe double to 180d so we can have debugging data. As long as we're not keeping forever.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by locating the UserReport PostgreSQL model and the existing event-retention cleanup path, then establish whether the retention period should be 90 or 180 days. Done means reports are deleted after the chosen maximum event-retention period without retaining them indefinitely.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, python
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.