Monitoring

Inspect logs and other Algolia data in Salesforce B2C Commerce.

Algolia Business Manager module

You can find the Algolia Business Manager under Merchant Tools > Algolia > Algolia.

Jobs reports

The v2 Job Reports section of the Algolia BM module contains information about the results of the last three job runs for each job. It summarizes the data in the log files generated by each job. Access this data from Administration > Operations > Jobs > [Job Name] > Schedule and History

The tables for each job contain the following columns:

Field title	Description
start	Start date and time of the job.
end	End date and time of the job.
products to be sent / total	Number of products (or categories) that are going to be sent for each locale and the number of total items processed. Due to product filtering, these numbers rarely match (for example, product masters aren’t sent by default). In the case of AlgoliaProductDeltaIndex_v2, the total is the number of records read from the B2C delta export XML files.
# locales	Number of locales configured for the site. If there are multiple locales, a single product to be sent will result in one record per locale.
records to be sent	Number of records that will be sent to Algolia. Usually the number of products to be sent multiplied by the number of locales.
records sent / failed	Number of records that were successfully sent to Algolia and the number of records that failed to be sent. If the latter is higher than zero, the value is highlighted in red.
chunks sent / failed	Number of chunks that were successfully sent to Algolia and the number of chunks that failed to be sent. If the latter is higher than zero, the value is highlighted in red.
error	If an error occurred during the job, the error message will be displayed here in red, empty otherwise.

If the cartridge is configured to index with the Ingestion API, the records sent and chunks sent counters in product job reports (AlgoliaProductIndex_v2, AlgoliaProductPriceIndex_v2, AlgoliaProductInventoryIndex_v2, and AlgoliaProductDeltaIndex_v2) reflect transport-level acceptance only. Indexing is asynchronous, so record-level errors (for example, “record too big” or failed transformations) appear later in the Algolia dashboard’s Connector Debugger, not in this report. Category and content job reports aren’t affected.

Data storage

Algolia job reports use B2C Custom Objects for storage. A custom object of type AlgoliaJobReport is created for each job run. The default retention period for these custom objects is 30 days, after which they’re automatically deleted.

Failover and recovery process

To solve inconsistency issues and ensure your indices are up-to-date, rebuild them.