Please help: Missing tracking events after update on 4.12.2

Hello,

it seems that after matomo auto updates from 4.11.0 to 4.12.2 that we have a problem with our event tracking.

I matomo appear much less events that in our internal event tracking. It’s very critical that matomo does not get/show the correct data anymore.

Do you have any idea for these problems? Are there any new feature (for example privacy settings or something) that might be the reason for our problems?

Thanks for some help!

Best regards,

Timo

#########################################

Here our system check:

### Mandatory checks

#### PHP version >= 7.2.5:
 ✔ 7.3.13

#### PDO extension:
 ✔ 

#### PDO\MYSQL extension:
 ✔ 

#### MYSQLI extension:
 ✔ 

#### Other required extensions:
 ✔ zlib ✔ json ✔ filter ✔ hash ✔ session

#### Required functions:
 ✔ debug_backtrace ✔ eval ✔ hash ✔ gzcompress ✔ gzuncompress ✔ pack

#### Required PHP configuration (php.ini):
 ✔ session.auto_start = 0 ✔ max_execution_time = 0 OR = -1 OR >= 30

#### Directories with write access:
 ✔ $DOC_ROOT/tmp ✔ $DOC_ROOT/tmp/assets ✔ $DOC_ROOT/tmp/cache ✔ $DOC_ROOT/tmp/climulti ✔ $DOC_ROOT/tmp/latest ✔ $DOC_ROOT/tmp/logs ✔ $DOC_ROOT/tmp/sessions ✔ $DOC_ROOT/tmp/tcpdf ✔ $DOC_ROOT/tmp/templates_c

#### Directories with write access for Tag Manager:
 ✔ $DOC_ROOT/js


### Optional checks

#### Required Private Directories:
 ✔ All private directories are inaccessible from the internet.

#### Recommended Private Directories:
 ✔ All private directories are inaccessible from the internet.

#### File integrity:
 ⚠ Warning: File integrity check failed and reported some errors. You should fix this issue and then refresh this page until it shows no error.<br/><br/>Files were found in your Matomo, but we didn't expect them.<br/>--> Please delete these files to prevent errors. 

#### 64-bit PHP Binary:
 ✔ 

#### Tracker status:
 ✔ 

#### Memory limit:
 ✔ 512M

#### Time zone:
 ✔ 

#### Open URL:
 ✔ curl

#### PageSpeed is turned off:
 ✔ 

#### GD > 2.x + FreeType (graphics):
 ✔ 

#### Other extensions:
 ✔ json ✔ libxml ✔ dom ✔ SimpleXML ✔ openssl

#### Other functions:
 ✔ shell_exec ✔ set_time_limit ✔ mail ✔ parse_ini_file ✔ glob ✔ gzopen ✔ md5_file

#### Filesystem:
 ✔ 

#### Set up Cron - Managing processes via CLI:
 ✔ Ok

#### Last Successful Archiving Completion:
 ⚠ Warning: Archiving last ran successfully on Monday, October 24, 2022 17:05:02 which is 1 days 10:32:26 ago.<br/><br/>Please check that you have setup a crontab calling the <code>core:archive</code> console command, and that you have configured a <code>MAILTO</code> to receive errors by email if archiving fails. You can also try to run the console command to archive your reports manually: <code>$DOC_ROOT/console --matomo-domain=analytics.promotionbasis.de core:archive</code>. Learn more.

#### Database abilities:
 ⚠ Warning: UTF8mb4 charset<br/><br/>Your database supports utf8mb4 charset, but your database tables have not been converted yet. You can do this by executing the command <code>$DOC_ROOT/console core:convert-to-utf8mb4</code> or activating the automatic conversion in General Settings.<br/><br/>This is required to be able to store 4-byte UTF8 characters. Unless utf8mb4 is available special characters, such as emojis, less common characters of asian languages, various historic scripts or mathematical symbols will be replaced with �. You can read more details about this topic in this FAQ.<br/> ⚠ Warning: LOAD DATA INFILE<br/>Hint: Using LOAD DATA INFILE by updating your PHP and MySQL software and ensuring your database user has the FILE privilege speeds up Matomo's archiving process a lot.<br/>You should fix this problem if your Matomo server tracks high-traffic websites (e.g. over 100,000 pages per month). ✔ CREATE TEMPORARY TABLES ✔ Changing transaction isolation level

#### Max Packet Size:
 ⚠ Warning: It is recommended to configure a 'max_allowed_packet' size in your MySQL database of at least 64MB. Configured is currently 32MB.

#### Forced SSL Connection:
 ⚠ Warning: We recommend using Matomo over secure SSL connections only. To prevent insecure access over http, add <code>force_ssl = 1</code> to the <code>General</code> section in your Matomo config/config.ini.php file.

#### Geolocation:
 ⚠ Warning: The default location provider determines the country visitors connect from based on their selected language. This is not very accurate, so install and use a geolocation database.

#### Update over HTTPS:
 ✔ 

#### Writable JavaScript Tracker ("/matomo.js"):
 ✔ 


### Informational results

#### Matomo Version:
 4.12.2

#### Matomo Update History:
 4.11.0,4.10.1,4.9.1,4.6.2,4.6.1,4.4.1

#### Matomo Install Version:
 3.13.1

#### Latest Available Version:
 4.12.2

#### Is Git Deployment:
 0

#### PHP_OS:
 Linux

#### PHP_BINARY:
 /opt/bitnami/php/sbin/.php-fpm.bin

#### PHP SAPI:
 fpm-fcgi

#### Timezone Version:
 2019.3

#### PHP Timezone:
 UTC

#### PHP Time:
 1666755448

#### PHP Datetime:
 2022-10-26 03:37:28

#### PHP INI max_execution_time:
 120

#### PHP INI post_max_size:
 40M

#### PHP INI max_input_vars:
 1000

#### PHP INI zlib.output_compression:
 

#### Curl Version:
 7.68.0, OpenSSL/1.1.1d

#### Suhosin Installed:
 0

#### DB Prefix:
 matomo_

#### DB Charset:
 utf8

#### DB Adapter:
 MYSQLI

#### MySQL Version:
 8.0.18

#### Num Tables:
 380

#### Browser Segment Archiving Enabled:
 1

#### Development Mode Enabled:
 0

#### Internet Enabled:
 1

#### Multi Server Environment:
 0

#### Auto Update Enabled:
 1

#### Custom User Path:
 0

#### Custom Include Path:
 0

#### Release Channel:
 latest_stable

#### Plugins Activated:
 API, Actions, AdvertisingConversionExport 4.1.0, Annotations, BulkTracking, Contents, CoreAdminHome, CoreConsole, CoreHome, CorePluginsAdmin, CoreUpdater, CoreVisualizations, CoreVue, CustomDimensions, CustomJsTracker, CustomReports 4.1.0, CustomVariables 4.1.1, Dashboard, DevicePlugins, DevicesDetection, Diagnostics, Ecommerce, Events, Feedback, GeoIp2, Goals, Heartbeat, ImageGraph, Insights, Installation, Intl, IntranetMeasurable, InvalidateReports 4.1.1, LanguagesManager, Live, Login, MarketingCampaignsReporting 4.1.3, Marketplace, MobileMessaging, Monolog, Morpheus, MultiSites, Overlay, PagePerformance, PrivacyManager, ProfessionalServices, Proxy, Referrers, Resolution, RssWidget, SEO, ScheduledReports, SegmentEditor, SitesManager, TagManager, Tour, Transitions, TwoFactorAuth, UserCountry, UserCountryMap, UserId, UserLanguage, UsersManager, VisitFrequency, VisitTime, VisitorInterest, VisitsSummary, WebsiteMeasurable, Widgetize

#### Plugins Deactivated:
 DBStats, MobileAppMeasurable, Provider 4.0.5

#### Plugins Invalid:
 

#### Server Info:
 Apache

#### Had visits in last 1 day:
 1

#### Had visits in last 3 days:
 1

#### Had visits in last 5 days:
 1

#### Archive Time Last Started:
 2022-10-26 03:05:01

#### Archive Time Last Finished:
 2022-10-24 17:05:02

#### User Agent:
 Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36

#### Browser Language:
 de-de,de,en-us,en

#### Total Invalidation Count:
 39

#### In Progress Invalidation Count:
 0

#### Scheduled Invalidation Count:
 39

#### Earliest invalidation ts_started:
 

#### Latest invalidation ts_started:
 

#### Earliest invalidation ts_invalidated:
 2022-10-24 18:05:24

#### Latest invalidation ts_invalidated:
 2022-10-25 13:05:01

#### Number of segment invalidations:
 34

#### Number of plugin invalidations:
 0

#### List of plugins being invalidated:
 

#### Anonymize Referrer:
 

#### Do Not Track enabled:
 0

Hi @iparker
Try to manually run the database migration (new columns in tables): core:update