Skip to content

2.10.18.3
Compare
Choose a tag to compare
@rbayet rbayet released this 10 Jan 13:44
· 97 commits to 2.10.x since this release
2.10.18.3
7bc0b3c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Main new feature

Tools to check and fix invalid behavioral data

When the Elasticsuite tracker is enabled on a site with a custom theme or on a PWA frontend, it can happen that the data collection is not correctly performed, particularly that some events are registred with an undefined or 'null' user session identifier (tracker session.uid parameter).
In turn those events coming from different visitors (tracker session.vid parameter) would still be collected as event for a same navigation session spanning several weeks or months, generating a document in the behavioral data session index with several hundreds or thousands of search terms, products added to cart, ordered, etc.

In the long run, it will slow down requests performed on the behavioral data indices up to generate 429 errors on your Elasticsearch/OpenSearch server preventing you to use, for instance, the Elasticsuite Search Usage analytics dashboard.
This release contains both a fix to prevent the collection of those ill-formed events and two Magento commands to be able to check and fix your already indexed behavioral data.

Check the presence of invalid behavioral data

You can run the elasticsuite:tracker:check-data Magento command to scan your behavioral indices for invalid data.
It will scan the behavioral data indices of all the active Magento store views and report if there are any errors.

If there are errors for a given store, they will be reported, as seen below :
image

Fix the invalid behavioral data.

If the elasticsuite:tracker:check-data command reports error, you can run the elasticsuite:tracker:fix-data command to fix the invalid data from your behavioral indices.
It will report what has been fixed.

For instance, on the same example as seen above, here are the results :
image

If there was nothing to fix, the command has no effect :
image

Future

As for the system message that can pop in your Magento admin interface when you have "Ghost Indices", we might in a future release make sure that admin users are made aware of existing invalid behavioral data without having to launch the elasticsuite:tracker:check-data Magento command.

📦 Features

  • [Tracker] Tools to check and fix invalid behavioral data by @rbayet in #3122
  • [Tracker] Prevent partial/invalid events to be indexed by @rbayet in #3111

🐛 Fixes

  • Fixes #3137 [Analytics] PHP8 compatibility popular search terms w/ re… by @rbayet in #3138
  • Fixes #3119 [GraphQL] allow drill-down in categories agg. of products… by @rbayet in #3120
  • Fixes #3123 [Search Merchandizing] Show back hidden products in preview by @rbayet in #3124
  • Fixes #3132 [Thesaurus] limit thesaurus rewriting loops by @rbayet in #3133
  • Fixes #3132 [Thesaurus] Rewriting loops avoidance unit tests by @rbayet in #3145
  • Fixes #2913 [Tracker] undefined array key date for elasticsuite tracker event index by @rbayet in #3112
  • [Tracker] Remove 'domain' parameter from tracker by @romainruaud in 7bc0b3c

Full Changelog: 2.10.18.2...2.10.18.3

Contributors

rbayet and romainruaud
Assets 2