Opened 6 years ago

Closed 3 years ago

Last modified 15 months ago

#5 closed New feature (fixed)

Tables log_ are not purged after archiving is done

Reported by: matt Owned by:
Priority: critical Milestone: 1.x - Piwik 1.x
Component: Core Keywords:
Cc: Sensitive: no

Description (last modified by matt)

The information contained in the tables _log_* should be purged automatically and regularly. Keeping all time logs in a single table significantly slows down the stats logging process (mysql having to rebuild indices, selecting from this million rows table is time consuming, maintenance is hard, etc.).

The goal of this task is to provide automatic purge of the tracking logs, every day or every month and with optional backup in a yearly table (customized with UI settings).

Processing uniques over weeks / months without using logs
In #409, we will implement a cookie store mechanism based on a mysql lookup table. This table will contain enough data (idvisitor, ip, idsite, date first visit, date last visit) to process unique visitors over a week or a month

Log purge execution
The purge task would be triggered during the 'Maintenance process' (see #1184), and once a day maximum it would execute and try to purge logs for the day (or month) before.

  • read settings (purge every day? every month?)
  • ensure all archives have been processed for the day archives contained in the log tables. Weeks/months are not necessary to be processed as they are the sum of daily archives (and uniques can be processed using the cookie store rather than keeping the full visitor logs for the period)
  • purge tracker for all websites at once
  • backs up the logs into a yearly archive table
    • INSERT INTO log_X_backups_2010 SELECT * FROM log_X
    • one backup per purged table (log_visit, log_conversion, etc.)
  • record the auto increment values (result of SELECT MAX() from log_X)
  • purge logs (TRUNCATE TABLE)
  • inserts last auto increment in each table

New Super User admin settings

  • Purge traffic logs and process reports at least every day/month
  • Backup traffic logs into a backup table containing all logs for the year (table is piwik_log_visit_backup2010)?
  • Could also add admin setting for 'Keep visitor cookies for 1 year' (from #409)

A few interesting resources

Attachments (1)

not yet rescheduler.png (15.1 KB) - added by matt 3 years ago.
Delete old logs piwik - Not yet rescheduled task

Download all attachments as: .zip

Change History (35)

comment:1 Changed 6 years ago by matt (mattab)

  • Milestone set to Future releases

comment:2 Changed 6 years ago by matt (mattab)

  • Description modified (diff)

comment:3 Changed 6 years ago by matt (mattab)

  • Description modified (diff)

comment:4 Changed 6 years ago by matt (mattab)

  • Description modified (diff)

comment:5 Changed 6 years ago by matt (mattab)

  • Milestone changed from Stable release to DigitalVibes

comment:6 Changed 5 years ago by matt (mattab)

  • Description modified (diff)

comment:7 Changed 5 years ago by spomoni

comment:8 Changed 5 years ago by spomoni

comment:9 Changed 4 years ago by weddingdress

comment:10 follow-up: Changed 4 years ago by vipsoft (robocoder)

  • Sensitive unset

After pruning, we can also use MySQL's "COMPRESS" on the corresponding archive tables. A side-effect is that the archive table is read-only, but that's ok if the raw visit information no longer exists to regenerate those archives.

comment:11 Changed 4 years ago by matt (mattab)

  • Description modified (diff)

comment:12 Changed 4 years ago by matt (mattab)

  • Description modified (diff)

comment:13 Changed 4 years ago by matt (mattab)

  • Description modified (diff)

comment:14 Changed 4 years ago by matt (mattab)

  • Milestone changed from 0 - Piwik 0.6.3 to 1 - Piwik 0.7 - DigitalVibes

comment:15 Changed 4 years ago by matt (mattab)

  • Milestone changed from 1 - Piwik 0.7 - DigitalVibes to Features requests - after Piwik 1.0
  • Priority changed from major to critical

Risk of this task is high, and time is too limited. Performance are fine long term, the downside of not purging logs is of course much higher disk space usage, but this is less an issue for 1.0 than performance.

delaying to post 1.0.

comment:16 in reply to: ↑ 10 Changed 4 years ago by itcoll

comment:17 Changed 3 years ago by matt (mattab)

This should probably be done at same time as #53

comment:18 Changed 3 years ago by matt (mattab)

  • Milestone changed from Feature requests to 1.x - Piwik 1.x

comment:19 Changed 3 years ago by matt (mattab)

  • Priority changed from critical to major
  • Type changed from Bug to New feature

comment:20 Changed 3 years ago by matt (mattab)

Note that when Purging is enabled, we should review the "Unique Visitors" processing or disable it when logs are not available for the requested date range.

http://piwik.org/faq/how-to/#faq_113

comment:21 Changed 3 years ago by matt (mattab)

Be careful when implementing this, with regards to archives that can be deleted after the fact in another ticket: #2328 - probably, in #2328, we should delete archives for days where the logs have already been deleted

comment:22 Changed 3 years ago by matt (mattab)

When this is implemented, we should update various FAQs that explain that it is safe to delete archive tables & have them re-processed from logs. It will not be the case, if logs have been deleted, and this should be clearly stated in all FAQs and documentations.

comment:23 Changed 3 years ago by peterb (peterbo)

(In [4856]) PrivacyManager / Delete old statistics from database; Refs #2233, #53, #5

comment:24 Changed 3 years ago by matt (mattab)

(In [4861]) Fixes #2233, Refs #5

  • enable new plugin on upgrade
  • Display message "your changes have been saved"
  • fix link redirect without idSite by using smarty function {url ...}

comment:25 Changed 3 years ago by peterb (peterbo)

(In [4868]) Refs #2233, #53, #5

  • tweaking / optimizing / commenting

comment:26 Changed 3 years ago by matt (mattab)

  • Resolution set to fixed
  • Status changed from new to closed

Fixed, we can always open another ticket for more advanced "pruning" and to move data to "archived" tables. Great to have this feature in 1.5!!

comment:27 Changed 3 years ago by matt (mattab)

  • Resolution fixed deleted
  • Status changed from closed to reopened

I see a potential bug: the task is set to "Not yet rescheduled" after I clicked "Yes" and clicked Save, and after reload the task is not scheduled. Thoughts?

(see attached screenshot)

Changed 3 years ago by matt (mattab)

Delete old logs piwik - Not yet rescheduled task

comment:28 Changed 3 years ago by peterb (peterbo)

  • Resolution set to fixed
  • Status changed from reopened to closed

(In [4884]) Fixes #5 - refactored the display "last run" and "next scheduled run" method. - Since the Scheduled Tasks Timetable is not immediately updated when the plugin is enabled, we can not rely on that value. Now the displayed times should be correct and we don't have to compensate the not yet set Schedule-Timetable value with the "not yet rescheduled" phrase.

comment:29 Changed 3 years ago by peterb (peterbo)

(In [4886]) Refs #5 - Make sure, log deletion will not be triggered before calculated "next scheduled deletion" time.

comment:30 Changed 3 years ago by matt (mattab)

  • Priority changed from major to critical

comment:31 Changed 3 years ago by kmartin

comment:32 Changed 3 years ago by kmartin

comment:33 Changed 2 years ago by matt (mattab)

see follow up ticket to purge log_action #2805

comment:34 Changed 15 months ago by Fabian Becker

In 3e371089ad99c853d639432e8865958bfd409214/puppetpiwik:

Make Git the default VCS for future builds.

refs #5

Note: See TracTickets for help on using tickets.