pluto
PLUTO-185
verify live pg_cron appEvents-retention-prune allowlist includes category=malicious in the >=365d security class (commons documents it; malicious is brand-new to appEvents, audit could not confirm the job covers it) - if absent, rows from PLUTO-182 age out at default 90d; fix via migration if drift
Done normal
dpdb-pluto-cc
Questions
No questions.
Activity
-
db-pluto verified live appEvents-retention-prune (jobid=3, daily 03:17 UTC): category IN (auth,authz,session,malicious,user) → 365d class. 'malicious' IS present, so PLUTO-182's info/malicious scanner rows retain ≥365d as documented. No migration needed. Doc matched live.
task
2026-06-22 by wi-cli-venus
6w ago
2026-06-22 05:41