seems like Traffic between Piwik <–> Piwik Database Server increased the same time.
Will check Logs if there is a Problem with Archiving somewhere … mhhh …
INFO [2018-08-17 09:39:56] 14195 ---------------------------
INFO [2018-08-17 09:39:56] 14195 SUMMARY
INFO [2018-08-17 09:39:56] 14195 Total visits for today across archived websites: 6031
INFO [2018-08-17 09:39:56] 14195 Archived today’s reports for 1107 websites
INFO [2018-08-17 09:39:56] 14195 Archived week/month/year for 1107 websites
INFO [2018-08-17 09:39:56] 14195 Skipped 0 websites
INFO [2018-08-17 09:39:56] 14195 - 0 skipped because no new visit since the last script execution
INFO [2018-08-17 09:39:56] 14195 - 0 skipped because existing daily reports are less than 3600 seconds old
INFO [2018-08-17 09:39:56] 14195 - 0 skipped because existing week/month/year periods reports are less than 3600 seconds old
INFO [2018-08-17 09:39:56] 14195 Total API requests: 4434
INFO [2018-08-17 09:39:56] 14195 done: 1107/1107 100%, 6031 vtoday, 1107 wtoday, 1107 wperiods, 4434 req, 2094677 ms, 123 errors.
INFO [2018-08-17 09:39:56] 14195 Time elapsed: 2094.677s
INFO [2018-08-17 09:39:56] 14195 ---------------------------
…
INFO [2018-08-17 09:39:56] 14195 Error: Got invalid response from API request: ?module=API&method=API.get&idSite=1&period=year&date=last3&format=php&trigger=archivephp. Response was ‘a:2:{s:6:“result”;s:5:“error”;s:7:“message”;s:113:“Mysqli prepare error: Table ‘piwik.piwik_archive_blob_2018_02’ doesn’t exist in engine - caused by plugin Actions”;}’
…
piwik.piwik_archive_blob_2018_02 is affected by: INNODB Table corruptions
Could those Errors trigger hgher Load / Traffic? mhhhh