Rule 10 - GCP Label and Tag Synchronization

Rule Synopsis

These are the rule/s that control whether one or more Labels and Tags in GCP are synchronized to each CMDB CI record, and if so, how CI Sync matches the content of each label (tag) to master data in ServiceNow.

GCP has the concept of Labels and Tags for Cloud Resources.

CI Sync therefore allows customers to synchronize either or both Labels and Tags.

Furthermore, because there can be an overlap of Labels and Tags in GCP (i.e. the same named Label and Tag can be used to seed the same destination attribute on a CI record), CI Sync allows customers to define whether the value of a give Label or Tag takes priority.

Rule Details and Default

  • By default, CI Sync does not synchronize any Labels or Tags from GCP.

Override Options

Context

Customers may consider overriding the default rule to describe one or more Labels and/or Tags to populate specific fields in ServiceNow (i.e. populate the value of a Label or a Tag against the specific field of a given CI in the CMDB).

CI Sync supports sophisticated RegEx expressions for the Label or Tag matching rules allowing customers to significantly enrich their CIs based on Lables and Tags being maintained against source system resources.

CI Sync’s rules cater for variations in Label and Tag names even for the same intended use. That is, CI Sync RegEx expressions will deal with a “Cost Center” being described in multiple Labels or Tags such as CostCenter, Cost Center, CostCenterTag and so on. This ensures customers with non-standardised use of Labels or Tags within their environment can still create significantly enriched data in their CMDB.

Options

  1. The rule can be amended so that CI Sync does sync Labels and/or Tags from GCP.

  2. Once Label or Tag sync’ing is enabled, customers can identify one or more these Labels and/or Tags containing the values to be used for a given specific fields. Out of the box CI Sync caters for the following specific GCP Label and Tag attribute use cases:

    1. Cost Center

    2. Environment

    3. Business unit

    4. Department

    5. Company

    6. Change control

    7. Owned by

    8. Assigned to

    9. Assignment group

    10. Managed by

    11. Managed by group

    12. Supported by

    13. Supported by group

Additional Label or Tag use cases (beyond the OOTB ones listed above) can also be added by Syncfish.

Overriding via Connection Settings

Customers can perform the override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is availabel via the following documentation:

  1. For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.

  2. For the specific CI Sync Connection Setting/s related to the rule described on this page please read:

    1. Label and Tag Synchronization for Cost Centre in GCP

    2. Label and Tag Synchronization for Environment in GCP

    3. Label and Tag Synchronization for Business Unit in GCP

    4. Label and Tag Synchronization for Department in GCP

    5. Label and Tag Synchronization for Company in GCP

    6. Label and Tag Synchronization for Change Control in GCP

    7. Label and Tag Synchronization for Owned By in GCP

    8. Label and Tag Synchronization for Assigned To in GCP

    9. Label and Tag Synchronization for Assignment Group in GCP

    10. Label and Tag Synchronization for Managed By in GCP

    11. Label and Tag Synchronization for Managed By Group in GCP

    12. Label and Tag Synchronization for Supported By in GCP

    13. Label and Tag Synchronization for Supported By Group in GCP

For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.

Additional Information

Syncfish strongly recommend customers read the following FAQ before commencing synchronization of Tag (or Label) data into ServiceNow.

FAQ - Overview of Cloud Tag and Label Synchronization Capabilities of CI Sync

N/A