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
Log cleaning in DB #7512
Comments
@devdesco-ceo This is a badly needed function for sure, not just for DB, but other logs as well. @magento-team I hope this is in the works. |
You bet! |
@devdesco-ceo thank you for your feedback. |
Preconditions
Steps to reproduce
Actual and Expected result
Resources |
In need of this badly |
@viktor-zhuromskyy Hello, The GitHub issue tracker is intended for technical issues only. Please refer to the Community Forums or the Magento Stack Exchange site for technical questions. |
@krutkoroma79911 This should be considered a feature request. One that is badly needed I might add. I don't know how much time I waste just clearing our junk that Magento should have a cron job for at the very least. |
@viktor-zhuromskyy, hi, The GitHub issue tracker is intended for technical issues only. Please refer to the Community Forums or the Magento Stack Exchange site for technical questions. |
@magento-engcom-team this is not a technical question but a feature request, it seems to me this issue has been closed erroneously, could you please reconsider? thanks!!! |
According to M2.0 guide at http://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands-log.html it suggests the way to clean logs in Database, but in M2.1.x there is no such function available under
./bin/magento
.My DB tables
report_event
,report_viewed_product_index
,customer_visitor
contain more than a few million entries combined. That is pure cluttering of Database. In M1 there is an option of automatic logs cleaning via cron.I want to keep up to datу logs in these tables only for past 30 days and no more...
What is the option for M2.1.x?
The text was updated successfully, but these errors were encountered: