Page MenuHomePhabricator

Add a GC for user logs
ClosedPublic

Authored by epriestley on Feb 1 2014, 11:23 PM.
Tags
None
Referenced Files
F15503746: D8128.diff
Mon, Apr 14, 12:40 PM
F15492433: D8128.id18398.diff
Sat, Apr 12, 2:19 PM
F15451799: D8128.diff
Fri, Mar 28, 11:52 PM
F15369630: D8128.id18398.diff
Mar 12 2025, 7:35 AM
Unknown Object (File)
Mar 2 2025, 12:36 PM
Unknown Object (File)
Feb 25 2025, 12:43 AM
Unknown Object (File)
Feb 23 2025, 10:20 PM
Unknown Object (File)
Feb 1 2025, 10:41 PM
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