Indexing Overview

klevu’s magento modules use klevu’s data indexing json api to register attributes and index entities with klevu before entity data for an attribute can be indexed to klevu, the attribute must be registered with klevu some standard attributes do not require registration with klevu, e g name, price, sku see indexing attributes https //docs klevu com/klevu magento v4/attributes for more details module structure the indexing module module m2 indexing enables the indexing of attributes and entities to klevu the indexing module creates a skeleton for other indexing modules to inject data into the indexing module itself has no knowledge of attribute or entity types the entities categories, cms pages and products are added via their own modules module m2 indexing categories , module m2 indexing cms and module m2 indexing products merchants can also add their own modules to index any custom entity types removing modules if you do not wish to index all entity types (products, categories, cms pages) to klevu you may remove the modules for those solutions by updating your composer json remove indexing categories "replace" { "klevu/module m2 indexing categories" " " }, remove indexing cms pages "replace" { "klevu/module m2 indexing cms" " " }, remove indexing products "replace" { "klevu/module m2 indexing products" " " }, if you are indexing data to klevu via some other method (e g xml shopping feed) then you can remove all klevu indexing modules composer remove "klevu/module m2 indexing" logging the indexing group of modules implement dedicated logs to segregate them from other areas, grouped by store name these logs are found at /var/log/klevu/\[store code]/klevu \[store code] indexing log to control the level of detail included in indexing logs (configurable on a store by store basis), please use the klevu > developer settings > logging > indexing log level setting see logging for more information