Decrease the Sentry RDS Storage (dupe 1)

[jennb33]

This ticket is a duplicate of 79198, for Sprint 9, due to developer access issues to DataDog or Citrix.

Issue Description

After the Sentry spike issue has been solved [with the Identity and Mobile teams?] the RDS storage can be decreased. This was increased due to the extreme storage required because of the issues (up to 6mm according to this Slack thread) that are taking up space.

---

Tasks

• [x] Investigate the Sentry Spike Issue by assessing the current storage in Sentry (see this dashboard)
• [x] Compare filtered to actual storage usage (volume)
• [ ] Decrease RDS storage
• [ ] Test as required
• [ ] Adjust monitors as necessary, once the findings between past and current storage usage has been established.

Acceptance Criteria

• [ ] Comparison of the past and current storage volumes to determine if the RDS needs to be decreased.
• [ ]

[Kshitiz-devops]

Before March 20 2024 the storage of rds database was 330 gb After the spike of march 20 the db size increased to more than 1 TB and the allocated storage is 2000 gb. Looking at the diagram Those spike data are still present in database due to which we are still occupying more than 900 gb in storage for rds. Looking at the stable diagram we can reduce the space to 1.5 tb but I think we should start with data cleanup from rds to better evaluate the required space for rds. With data clean up I think we can reduce the allocated space for rds to be 1tb. Current retention period is set to default to 90 days. In conclusion I think we can lower it to 1.5 tb then after cleanup we can go lower.

[Kshitiz-devops]

Chart we are using: https://github.com/sentry-kubernetes/charts