Change Details

Currently we have the ability to manually archive link events by month and year. The link events table currently has `6580783`, which includes events for `205` days (we have archived all events from before 2024). That's approximately `32000` events per day on average. Performance should improve significantly if we can reduce the table size so drastically. **Acceptance criteria** [] identify and remediate any code that uses linkevents after 1 day [] update link event archive management command to name files uniquely per day [] add cron task for archiving events daily

Currently we have the ability to manually archive link events by month and year. The link events table currently has `6580783`, which includes events for `205` days (we have archived all events from before 2024). That's approximately `32000` events per day on average. Performance should improve significantly if we can reduce the table size so drastically. **Acceptance criteria** [x] identify and remediate any code that uses linkevents after 1 day [x] update link event archive management command to name files uniquely per day [x] add cron task for archiving events daily

Currently we have the ability to manually archive link events by month and year. The link events table currently has `6580783`, which includes events for `205` days (we have archived all events from before 2024). That's approximately `32000` events per day on average. Performance should improve significantly if we can reduce the table size so drastically. **Acceptance criteria** [x] identify and remediate any code that uses linkevents after 1 day [x] update link event archive management command to name files uniquely per day [x] add cron task for archiving events daily