-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Records auto-cleaner #317
Comments
This already exists: https://laravel.com/docs/10.x/pulse#trimming |
Yeah I know @driesvints , but it's not working on our side. Maybe I don't understand the documentation. We have records almost a month old. I think the maximum age is 7 days. |
Just for clarification, we have the default configuration:
Also, I'm trying to check the code to see how it works, because to my eyes, it's not clear how the lottery works. If I discover how it works, I may make a PR to the documentation to help. |
@driesvints We've been trying to investigate how it works but we don't reach solid conclusions: We have also realized that we have to manually restart the deamon from forge in order to make it get the new php code after each deployment. So: Thanks in advance! |
Hmm it seems there is a bug. I used xdebug and it never hits the trim method. If I remove ... from trim() here it works. It is already inside a closure :) //either do
->winner(fn () => $this->rescue($ingest->trim(...))
//or
->winner(fn () => $this->rescue(fn () => $ingest->trim())) @didac-adria You can restart with |
Oh great! I'm adding pulse:restart to our deployment hooks. Thanks! |
Closing this as we have a fix up. Heads up that this mainly impacts apps writing directly to the database and not using the performance focused Redis ingest. Sorry for the troubles, folks. |
Hey team! See you! |
Hi!
I know this is in betta still, but I think the basic implementation of Pulse should contain a DB records cleaner. Otherwise they pile-up. Do you guys have something in mind already to incorporate a command to clean records older than 7 days (I think is the maximum amount of days to see data in the dashboards)? Or am I missing something and records should be deleted but somehow they aren't in our backend?
The text was updated successfully, but these errors were encountered: