Cleanup tool to prune tbllog_register table
-
bluesteam shared this idea 7 years ago
- Other
- 17 Comments
143
Votes
Login to Vote
This table gets EXTREMELY large in row size.
When performing certain clean up tasks by going to Utilities -> System -> System Cleanup we have tools that can clean up the following:
FileSystem - Prune Old Attachments
FileSystem - Empty Template Cache
tblactivitylog - Prune Client Activity Logs
tblemails - Prune Saved Emails
tblgatewaylog - Empty Gateway Log
tblticketmaillog - Empty Ticket Mail Import Log
tblwhoislog - Empty WHOIS Lookup Log
but there is nothing for the tbllog_register table. On a clean install of WHMCS, the table already starts out at +-2300 records and over time this grows immensely. My own table is sitting on 206 782 rows as we speak and it's clear that this table needs to be included in the list of cleanup tools as it can hinder restores when it needs to insert hundreds of thousands of rows. having a large table can also reduce performance and thus we should have the abilitiy to clean it up.
When performing certain clean up tasks by going to Utilities -> System -> System Cleanup we have tools that can clean up the following:
FileSystem - Prune Old Attachments
FileSystem - Empty Template Cache
tblactivitylog - Prune Client Activity Logs
tblemails - Prune Saved Emails
tblgatewaylog - Empty Gateway Log
tblticketmaillog - Empty Ticket Mail Import Log
tblwhoislog - Empty WHOIS Lookup Log
but there is nothing for the tbllog_register table. On a clean install of WHMCS, the table already starts out at +-2300 records and over time this grows immensely. My own table is sitting on 206 782 rows as we speak and it's clear that this table needs to be included in the list of cleanup tools as it can hinder restores when it needs to insert hundreds of thousands of rows. having a large table can also reduce performance and thus we should have the abilitiy to clean it up.
Merged Ideas
DB tbllog_register, this function requires automatic cleaning (Needs a cleanup feature.).
HiDB, tbllog_registerThis function requires automatic cleaning (Needs a cleanup feature.).It only takes a few months for it to become big data/size.Thanks
HiDB, tbllog_registerThis function requires automatic cleaning (Needs a cleanup feature.).It only takes a few months for it to become big data/size.Thanks
28 Comments
Login to post a comment.
https://rummy91apk.app/
https://rummygameszone.com/
tbllog_registerwas at 1.4 million records.WHMCS should recognise this as a bug and fix it immediately.
Personally I want to keep emails for clients for the last 4 years.
I also noticed WHMCS keeps all admin logins and IPs with no way to flush them from the GUI, i can see i first installed WHMCS in 2008 and all logins since then are logged! As nice as it was to see i'm a loyal long term WHMCS user i'd like to maybe only keep 1 year of admin login logs too.
A lot of the billing in WHMCS is monthly, so I recommend setting it to 3 months.
That means that if a monthly problem is noticed after 2 or 3 months there are still plenty of log entries to fully investigate.
This should keep the log under 20MB for most typical installations, which I think is acceptable to most people.
Alternatives or extra features -
1) Add it to the section Utilities -> System -> System Cleanup -> Advanced
2) Add an automatic database size check to the upgrade script (and anywhere else that's relevant) before it does a database update, then automatically prune the database, or tell the user exactly how to prune the database.
Thanks for your feedback and commentary. This table contains the data for the Automation Status page's history.
For how long would you like this data to be retained by default?
A lot of the billing in WHMCS is monthly, so I recommend setting it to 3 months.
That means that if a monthly problem is noticed after 2 or 3 months there are still plenty of log entries to fully investigate.
This should keep the log under 20MB for most typical installations, which I think is acceptable to most people.
Alternatives or extra features -
1) Add it to the section Utilities -> System -> System Cleanup -> Advanced
2) Add an automatic database size check to the upgrade script (and anywhere else that's relevant) before it does a database update, then automatically prune the database, or tell the user exactly how to prune the database.