Add automatic data retention/cleanup feature #545
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
DATA_RETENTION_DAYSconfig option to automatically clean up old request dataProblem
The FMD database grows unbounded over time, causing slow startup (15+ seconds when tables have millions of rows):
Solution
Add a config option for data retention:
When
DATA_RETENTION_DAYS > 0, cleanup is automatically scheduled ondashboard.bind(app).Changes
flask_monitoringdashboard/core/config/__init__.py- Add config optionflask_monitoringdashboard/core/database_pruning.py- Add batch delete function and schedulerflask_monitoringdashboard/__init__.py- Auto-schedule cleanup in bind()config.cfg- Add example configtests/unit/core/test_database_pruning.py- New test file (6 tests)tests/unit/core/config/test_config.py- Add config parsing tests (3 tests)Test plan
🤖 Generated with Claude Code