#Map Similarity Driven Instances

If the matching theory method of a tenant is set to Similarity-based matching, you can review and map system-generated similarity-driven instances.

On the Tenants page, select the tenant and click Settings > Map similarity-driven instances. The Map similarity-driven instances window pops up, displaying tenant and baseline instances (referring to the baseline that has already been deployed to the tenant) that cannot be matched by name, with a system-generated similarity score displayed to identify potential matches. This allows you to manually review and map these similarity-driven instances for further comparison.

The Similarity-based matching window keeps popping up until all instances are mapped or the matching theory method is changed back to Name-based matching. You can click Skip if you want to skip this step for this time.

The Last sync time field shows the time when data was synced. If you want to recalculate similarity, click Recalculate similarity, and then a process will start.

For efficient management, you can adjust the similarity floor. Only tenant and baseline instances with a similarity score above this threshold will appear below.

For each pair, the tenant instance appears on the left, while baseline instances are listed on the right in a drop-down list, sorted by highest similarity score at the top. You can select different baseline instances to view their similarity score. To check the detailed differences between the tenant and baseline instances, click the Compare button to open the Compare window. If a tenant instance can be mapped to a baseline instance, click the Map button. Once mapped, the baseline instance will be available in other pairs.

To remove a mapping between a tenant instance and a baseline instance, click the Unmap button next to the pair.

After saving, the comparison page will be regenerated where all mapped instances will be displayed in the Conflicts tab, while unmapped instances will be listed under the Unique to baseline and Unique to tenant tabs.

After saving, click Confirm in the pop-up confirmation window. All previous deviation results for this tenant will be cleared. You can start a drift detection job now or wait for the next scheduled drift detection job. Afterward, mapped instances will be displayed in the Conflicts tab, while unmapped instances will be listed under the Unique to baseline and Unique to tenant tabs.