Rule Synopsis
These are the rule/s (or CI Sync feature) that causes CI Sync to test multiple CMDB CI tables/classes for the following two purposes:
-
To search for an existing CIs during a CI Update Operation.
-
To write new CIs during a CI Insert Operation.
Rule Details and Default
|
Source System |
Default behavior |
Link for further details |
|---|---|---|
|
AWS |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each AWS resource type. |
The single destination CMDB CI table/class (per AWS resource) is based on the mapping table described in this rule: Rule 3 - Mapping of AWS Resource Types to CMDB CI Classes |
|
Azure |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each Azure resource type. |
The single destination CMDB CI table/class (per Azure resource) is based on the mapping table described in this rule: Rule 3 - Mapping of Azure Resource Types to CMDB CI Classes |
|
GCP |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each GCP resource type. |
The single destination CMDB CI table/class (per GCP resource) is based on the mapping table described in this rule: Rule 3 - Mapping of GCP Resource Types to CMDB CI Classes |
|
InTune |
By default, CI Sync does perform cross-class matching. CI Sync targets a mutliple destination CMDB CI tables/classes for various InTune Asset types. |
The multiple destination CMDB CI tables/classes (per inTune Asset Type) is based on the mapping table described in this rule: Rule 2 - Mapping of InTune Corporate and BYOD Asset Types to ServiceNow CMDB CI Classes |
|
Lansweeper On-Prem |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each Lansweeper Asset type. |
The single destination CMDB CI table/class (per Lansweeper Asset Type) is based on the mapping table described in this rule: Rule 3 - Mapping of Lansweeper On-Prem Asset Types to CMDB CI Classes. |
|
Lansweeper Cloud |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each Lansweeper OT Asset type. |
The single destination CMDB CI table/class (per Lansweeper OT Asset Type) is based on the mapping table described in this rule: Rule 3 - Mapping of Lansweeper Cloud Asset Types to CMDB CI Classes |
|
MS Defender for Cloud Apps |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each MS Defender for Cloud Apps resource type. |
The single destination CMDB CI table/class (per MS Defender for Cloud Apps resource) is based on the mapping table described in this rule: Rule 3 - Mapping of Defender for Cloud Apps Resource Types to ServiceNow CMDB CI Classes |
|
MS Defender for Endpoint |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each MS Defender for Endpoint resource type. |
The single destination CMDB CI table/class (per MS Defender for Endpoint resource) is based on the mapping table described in this rule: Rule 2 - Mapping of Defender for Endpoint Asset Types to ServiceNow CMDB CI Classes |
|
Nutanix |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each Nutanix asset type. |
The single destination CMDB CI table/class (per Nutanix asset type) is based on the mapping table described in this rule: Rule 3 - Mapping of Nutanix Asset Types to CMDB CI Classes |
|
Omnissa Workspace ONE |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each Workspace ONE assest type. |
The single destination CMDB CI table/class (per Workspace ONE asset type) is based on the mapping table described in this rule: Rule 2 - Mapping of Omnissa Workspace ONE Asset Types to ServiceNow CMDB CI Classes |
|
SolarWinds Orion |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each SolarWinds assest type. |
The single destination CMDB CI table/class (per SolarWinds asset type) is based on the mapping table described in this rule: Rule 3 - Mapping of SolarWinds Asset Types to CMDB CI Classes |
|
VMware vSphere |
By default, CI Sync does not perform cross-class matching. Instead, CI Sync targets a single destination CMDB CI table/class for each VMware record type. |
The single destination CMDB CI table/class (per VMware recrod type) is based on the mapping table described in VMware Data Rule: Rule 3 - Mapping of VMware Asset Types to CMDB CI Classes |
Override Options
Context
Customers may consider enabling cross-class matching (when it is not enabled by default) so CI Sync targets multiple CMDB CI Tables/Classes. This can often be required when existing CIs are already present in CMDB CI Tables/Classes different to those targeted by the default CI Sync CMDB CI Class mappings described by the relevant system specific rule.
Options
-
This Data Sync Rule can be overridden so that CI Sync does perform cross-class matching (when it is not enabled by default on a given source system).
-
If cross-class matching is enabled the rules can be further refined as follows:
-
Customer’s (assisted by a Syncfish expert) can define the multiple destination CMDB CI Tables/Classes that CI Sync should target when attempting to locate an existing CI based on the incoming Asset.
-
CI Sync can also enable CI relocation (or not), automatically relocating a matched CI from its current CMDB Table/Class to a new/default CMDB Table/Class.
-
Overriding via Connection Settings
N/A
Additional Information
N/A
Related Rules
-
All of those included in the above table.
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: No (a plan is needed - see below)
Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule
Answer: Either a Silver Plan or Gold Plan