Rule Synopsis
These are the rule/s that determine the target CMDB CI Tables/Classes used by CI Sync for each GCP Resource Type.
The target CI Table/CI Class is used by CI Sync for 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
The default table mappings for Primary/Parent Resource Types are shown below.
|
Primary/Parent Resource Types |
Default Target Class/Classes |
|---|---|
|
Organization |
|
|
Organizations |
cmdb_ci_cmp_resource |
|
Regions |
cmdb_ci_logical_datacenter |
|
Projects |
cmdb_ci_gcp_project |
|
App Engine |
|
|
Applications |
cmdb_ci_cloud_appserver |
|
Storage |
|
|
Buckets |
cmdb_ci_cloud_storage_account |
|
Compute |
|
|
VM Instances |
cmdb_ci_vm_instance |
|
Cloud Functions |
cmdb_ci_web_service |
|
Kubernetes#1 |
|
|
Clusters |
cmdb_ci_kubernetes_cluster |
|
Node Pools |
cmdb_ci_kubernetes_node_pool |
|
Volumes |
cmdb_ci_kubernetes_volume |
|
VPC Network |
|
|
Networks |
cmdb_ci_network |
|
Redis |
|
|
Redis Instances |
cmdb_ci_cloud_database |
|
Big Query |
|
|
Big Query Datasets |
cmdb_ci_cloud_database |
|
Cloud SQL |
|
|
Cloud SQL Database |
cmdb_ci_cloud_database |
The default table mappings for Secondary/Child Records are shown below.
|
Secondary/Child Records |
Default Target Class |
|---|---|
|
Labels |
cmdb_key_value |
|
Tags |
cmdb_key_value |
|
Zones (for Regions) |
cmdb_ci_availability_zone |
|
Services (for App Engine Applications) |
cmdb_ci_web_service |
|
Subnets (for VPC Networks) |
cmdb_ci_cloud_subnet |
|
Models (for Big Query Datasets) |
cmdb_ci_function_ai |
|
Namespaces (for Kubernetes Clusters)#1 |
cmdb_ci_kubernetes_namespace |
|
Deployments (for Kubernetes Clusters)#1 |
cmdb_ci_kubernetes_deployment |
|
Ingresses (for Kubernetes Clusters)#1 |
cmdb_ci_kubernetes_ingress |
|
Services (for Kubernetes Clusters)#1 |
cmdb_ci_kubernetes_service |
|
Pods (for Kubernetes Clusters)#1 |
cmdb_ci_kubernetes_pod |
|
Nodes (for Node Pools)#1 |
cmdb_ci_kubernetes_node |
Footnote #1
The Kubernetes CI Classes used by CI Sync are only available in ServiceNow if the ServiceNow “Discovery and Service Mapping Patterns” plug-in is currently installed or has been installed in the past.
This means there is a hard pre-requisite for customers to have installed the above ServiceNow plug-in to use CI Sync to synchronize Kubernetes resources.
Override Options
Context
Customers may consider changing these mappings to target different CMDB CI Tables/Classes shown above. This can often be required when existing CIs are already present in the CMDB (in Classes different to those shown below) and CI Sync is expected to correlate to the existing CIs.
Options
-
The target CI Class can be amended per GCP Resource Type.
Overriding via Connection Settings
Not Available - Requires a Custom Data Sync Rule (and therefore a Syncfish Support Plan to modify the default behaviour)
Additional Information
N/A
Related Rules
N/A