Delivery Log Tables Clear Downs

[Michael Wilding]

Has anybody done anything with their log tables to reduce table size?

We've got log and archive log tables totalling around 30Gb. While this doesn't cause particular issues in day-to-day running, if we need to take/restore a backup it causes a big problem.

I'm wondering what the relevance of keeping these log files are, and if there's a way we can move them off site to keep the live database as slimline as possible.

Thanks
Michael

 

[twisted1919]

If using 1.4.9 you can enable deleting these logs from backend > settings > cron.
Mailwizz will delete all the delivery logs for campaigns that finished 5 days ago or more and replace those logs with static counters, so you will see the counters but you won't see the actual logs in the app anymore.

 

[Michael Wilding]

Superb, is there any downside to deleting these logs? We won't lose open/click info etc... just whether an email was delivered successfully or not?

 

[twisted1919]

just whether an email was delivered successfully or not?

Yup, just this.

 

[Michael Wilding]

Perfect, thank you.

 

[Michael Wilding]

@twisted1919 will this clear archive logs as well?

 

[Michael Wilding]

Wondering if I need to set a CRON up to run this, set to 90 days since I upgraded but still go back to Jan 1st. Or does it run just once a month?

 

[twisted1919]

@twisted1919 will this clear archive logs as well?

Yes.

Wondering if I need to set a CRON up to run this,

You don't have to, it runs when the daily cron job runs.

 

[Michael Wilding]

Hmm, not sure mine is working, still got logs going back to Jan 2017 even though it’s set to delete after 90 days. Any ideas?

 

[twisted1919]

Any ideas?

Run the command manually separately, like:

/usr/bin/php -q /absolute/path/to/console/console.php delete-campaign-delivery-logs --verbose=1

 

[Michael Wilding]

Working manually, should I just add this as a CRON?

 

[twisted1919]

Working manually, should I just add this as a CRON?

Nope. this work from daily cron job too, just make sure you enabled it from backend > settings > cron. If you do it from there, it will work.

 

[Michael Wilding]

Okay, I've cleared it manually now. I will keep an eye on it.

 

[Michael Wilding]

Ah, I missed the extra setting at the top, thought it was just the timeframe.