-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Limit the stored history #145
Comments
Those files are session history files and are created based on the process id and creation time. I assume, in your case, a new process runs the command each time, which will result in a new session history file. @jimaek @MartinKolarik maybe we can add a flag i.e |
For the time being, I’ve set up a cron job that runs every 2 hours to delete those directories. Is there a local patch or configuration change I can implement to prevent the creation of the session history files altogether? |
Not at the moment, but I'm sure we will address it in the next release shortly. It would probably be best to solve the issue of accumulating files for everyone. Something like a max 100 and delete everything else. I don't think anyone needs more than 10 previous values to be honest. Or maybe even use an embedded DB? What does everyone think? |
One idea would be to not store session history files by default. Instead, a new parameter, --save-session, could be introduced to enable the storage of session history files only when needed. Alternatively, a single logging file could be used to store the history of all sessions (if needed). |
@radulucut let's add automated cleanup:
Feel free to adjust the storage structure to make implementing these rules easier.
|
Hi,
About a week ago, I installed Globalping on my Ubuntu VM, which also runs Zabbix Server. I've created several items that execute the following commands every 10 minutes:
system.run["globalping ping {$TARGET} -J -L 1 -F '396982+Berlin'"]
This setup runs for ICMP and MTR across five fixed locations (ASN + city), resulting in a total of 15 calls every 10 minutes. However, I’ve noticed that Globalping is storing its measurements in the /tmp directory without automatically clearing them. Over the past 10 days, this has resulted in the creation of approximately 1.3 million directories, all named in the format globalping_688491_1729766790000, each containing a measurements file.
Is there a configuration or setting that can be adjusted to automatically clear these directories after a certain period of time? Or maybe to not store them?
Thank you for your assistance.
Best regards,
Valeriu
The text was updated successfully, but these errors were encountered: