Page MenuHomePhabricator

Add a GC for user logs
ClosedPublic

Authored by epriestley on Feb 1 2014, 11:23 PM.
Tags
None
Referenced Files
Unknown Object (File)
Nov 28 2024, 12:15 AM
Unknown Object (File)
Nov 26 2024, 12:42 PM
Unknown Object (File)
Nov 26 2024, 12:42 PM
Unknown Object (File)
Nov 26 2024, 12:42 PM
Unknown Object (File)
Nov 26 2024, 12:20 PM
Unknown Object (File)
Nov 21 2024, 10:35 PM
Unknown Object (File)
Nov 18 2024, 2:38 PM
Unknown Object (File)
Nov 17 2024, 1:12 AM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
T4368: Implement GC for mail
Commits
Restricted Diffusion Commit
rP5a9a96735dde: Add a GC for user logs
Summary

Fixes T4368. This is the last "obvious" table we have which we should be GC'ing but do not. It's about 1/12th of the data on secure.phabricator.com.

This table stores logins, account creation, password resets, login attempts, etc, and is primarily useful if something sketchy happens so you can go back and review login activity. This data is not useful indefinitely, and there's no reason to retain it forever. Because you don't always know when something sketchy happened I've given this table a fairly long TTL (180 days), but we don't need limitless amounts of this data.

Test Plan

Ran phd debug garbage and saw a reasonable amount of data get GC'd. This table already has an appropriate key.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped