Homec4science

Garbage collect Drydock logs after 30 days

Authored by epriestley <git@epriestley.com> on Oct 1 2015, 17:09.

Description

Garbage collect Drydock logs after 30 days

Summary:
Ref T9252. Drydock logs are almost exclusively useful as a diagnostic tool for debugging immediate problems, so GC them fairly aggressively.

(I expect 99% of the usefulness of these logs to be within the first 24 hours, basically "why isn't my thing working". I can't really think of any cases where having old logs would be useful.)

Test Plan:

  • Ran GC, saw it hit the log table (with no effect).
  • Changed TTL from 30 days to 30 seconds, ran GC, saw it wipe recent logs.

Reviewers: chad

Reviewed By: chad

Maniphest Tasks: T9252

Differential Revision: https://secure.phabricator.com/D14197

Details

Committed
epriestley <git@epriestley.com>Oct 1 2015, 17:09
Pushed
aubortJan 31 2017, 17:16
Parents
rPH2ef5b5321d1f: Move Drydock logs to PHIDs and increased structure
Branches
Unknown
Tags
Unknown

Event Timeline

epriestley <git@epriestley.com> committed rPH06f927250290: Garbage collect Drydock logs after 30 days (authored by epriestley <git@epriestley.com>).Oct 1 2015, 17:09