pruning the result_history_items table

[ndeblauw]

I just noticed one of my databases was growing. When looking for the cause, I noticed that the healt_check_result_history_items table was already at 31,6 MB, monitoring started on February 1st. And every result since then was present.

I immediately checked my config file, but that was correctly configured (aka keep_history_for_days' => 5,).

I dived a bit deeper, and noticed that keeping the history (c)lean and mean is done through pruning. But this is not mentioned in the documentation - first I thought I read over it, but then I went looking for it and I also couldn't find it with the search.

I decided to quickly do run the prune command (php artisan model:prune) but that resulted to my surprise in no prunable models found. Hmm. I quickly applied pruning to one of my own models and then this command did work.

I did a new try and thereby explicitly mentioning the model to prune, and this worked:
php artisan model:prune --model=Spatie\Health\Models\HealthCheckResultHistoryItem

However, this isn't really a friendly command to ask users to add to their scheduler. So I would propose to add a command to laravel-health (e.g. health:prune or health:prune-history) with the recommendation to run add this command to the scheduler to run it daily.

If you like this approach, I can make a PR for it. Or am I really talking nonsense/missing something? :-)

[freekmurze]

I'll improve our docs and mention how you can explicitly specify our model when running the prune command.

[ndeblauw]

Super, thank you! Myself, I switched actually to the no-store option as getting a notification is enough for my use cases. But I learned a lot with this case, and started using pruning for multiple models, it was the kick in the ### I needed for this :-) Have a nice weekend!