[GH-ISSUE #938] Prune outdated history #659

Closed
opened 2026-02-25 23:43:11 +03:00 by kerem · 2 comments
Owner

Originally created by @RoboMagus on GitHub (Jan 7, 2024).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/938

I've been looking around for an option where outdated status history (e.g. older than X days) could be auto deleted to avoid infinitely growing DBs on large systems.

I could be overlooking something, but if such a feature is not yet implemented it'd be a nice addition :)

Originally created by @RoboMagus on GitHub (Jan 7, 2024). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/938 I've been looking around for an option where outdated status history (e.g. older than X days) could be auto deleted to avoid infinitely growing DBs on large systems. I could be overlooking something, but if such a feature is not yet implemented it'd be a nice addition :)
kerem closed this issue 2026-02-25 23:43:11 +03:00
Author
Owner

@cuu508 commented on GitHub (Jan 7, 2024):

Entries from the api_ping and the api_notification tables are being deleted automatically, see: github.com/healthchecks/healthchecks@ae94648efd/hc/api/models.py (L507)

Entries from the api_flip table are not being deleted automatically, but there is a pruneflips management command for that: https://github.com/healthchecks/healthchecks#database-cleanup

<!-- gh-comment-id:1880014478 --> @cuu508 commented on GitHub (Jan 7, 2024): Entries from the `api_ping` and the `api_notification` tables are being deleted automatically, see: https://github.com/healthchecks/healthchecks/blob/ae94648efd19bc6f2fbe3f740065adf43a5b6b57/hc/api/models.py#L507 Entries from the `api_flip` table are not being deleted automatically, but there is a `pruneflips` management command for that: https://github.com/healthchecks/healthchecks#database-cleanup
Author
Owner

@RoboMagus commented on GitHub (Jan 7, 2024):

Thanks! I figured something like that would've been implemented already, but I was not able to find it in the healthchecks.io documents.

<!-- gh-comment-id:1880073369 --> @RoboMagus commented on GitHub (Jan 7, 2024): Thanks! I figured something like that would've been implemented already, but I was not able to find it in the healthchecks.io documents.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#659
No description provided.