[GH-ISSUE #505] prunepings does not delete logs from web UI #370

New issue

Closed

opened 2026-02-25 23:42:12 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:42:12 +03:00

Owner

Originally created by @yonas on GitHub (May 3, 2021).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/505

After running the script, I still see log entries in the web UI when looking at a check's details page.

On first run, it reports having deleted a couple thousand pings. On second run, immediately after, it reports 0 pings pruned.

It seems like the web UI is either caching pings or using another source to fetch ping logs.

Originally created by @yonas on GitHub (May 3, 2021). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/505 After running the script, I still see log entries in the web UI when looking at a check's details page. On first run, it reports having deleted a couple thousand pings. On second run, immediately after, it reports 0 pings pruned. It seems like the web UI is either caching pings or using another source to fetch ping logs.

kerem closed this issue

2026-02-25 23:42:13 +03:00

kerem commented

2026-02-25 23:42:13 +03:00

Author

Owner

@cuu508 commented on GitHub (May 3, 2021):

prunepings deletes old pings, leaving the 100 most recent for every check.

After running prunepings nothing should change in the web UI because the web UI is showing the last 100 pings for each check, and prunepings does not touch these. It only deletes pings that the web UI would not show any more anyway.

@cuu508 commented on GitHub (May 3, 2021): `prunepings` deletes old pings, leaving the 100 most recent for every check. After running `prunepings` nothing should change in the web UI because the web UI is showing the last 100 pings for each check, and `prunepings` does not touch these. It only deletes pings that the web UI would not show any more anyway.

kerem commented

2026-02-25 23:42:13 +03:00

Author

Owner

@yonas commented on GitHub (May 3, 2021):

Thanks, I've created a pull request to add that info to the final output so new users don't need to check the README. https://github.com/healthchecks/healthchecks/pull/506

@yonas commented on GitHub (May 3, 2021): Thanks, I've created a pull request to add that info to the final output so new users don't need to check the README. https://github.com/healthchecks/healthchecks/pull/506

kerem commented

2026-02-25 23:42:13 +03:00

Author

Owner

@cuu508 commented on GitHub (May 5, 2021):

New users definitely should read README :-)

""Done! Pruned %d pings. Kept 100 most recent pings." has a couple problems:

It makes it sound like 100 pings total were kept. It is 100 pings per check. So a more precise wording would be "For each check, kept 100 most recent pings."
100 is the default value but it can be tweaked per user (the Profile.ping_log_limit field). So "kept 100 most recent pings" may sometimes be inaccurate. README also has this problem, I'll update README with a note about 100 being a per-user configurable value.

I'm leaning towards leaving the management command as-is.

@cuu508 commented on GitHub (May 5, 2021): New users definitely *should* read README :-) ""Done! Pruned %d pings. Kept 100 most recent pings." has a couple problems: * It makes it sound like 100 pings total were kept. It is 100 pings per check. So a more precise wording would be "For each check, kept 100 most recent pings." * 100 is the default value but it can be tweaked per user (the Profile.ping_log_limit field). So "kept 100 most recent pings" may sometimes be inaccurate. README also has this problem, I'll update README with a note about 100 being a per-user configurable value. I'm leaning towards leaving the management command as-is.

kerem referenced this issue

2026-02-25 23:44:13 +03:00

[PR #372] [CLOSED] Migrating unique_key to be a database property #940

kerem referenced this issue

2026-02-25 23:44:13 +03:00

[PR #379] [MERGED] Implementing new changes discussed to resolve #370 #941