---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Performing real-time updates to tags for cloud resources

# Performing real-time updates to tags for cloud resources {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

You can set up cloud events processing and map a tag policy to update tags for cloud resources in real time.

## Prerequisites {#tag-governance-real-time-updates__section_cly_dpk_hcc}

* Cloud events table \[sn_cmp_cloud_events\] table does not have any records in the processed state.
* CIs impacted by tag change events are identified by either CAPI or Discovery and Service Mapping patterns.
* Configured at least one tag policy.
* Select the Run on cloud events check box in the tag policy you create.
{#tag-governance-real-time-updates__ul_hgr_b1t_cqb}

## Instructions depend on the cloud provider {#tag-governance-real-time-updates__section_kfq_3ws_cqb}

See the following setup instructions for cloud event processing:

* [AWS events-driven discovery](https://servicenow-prod.fluidtopics.net/wLyaKKWolkmvMCS7STyfmg "The Amazon Web Services (AWS) Config service can raise events for any changes in the life-cycle state or the configuration of a cloud resource. The ServiceNow event-driven discovery uses the events to auto-update the latest resource information in the Configuration Management Database (CMDB).")
* [Configure the Microsoft Azure Alert service to auto-update the CMDB](https://servicenow-prod.fluidtopics.net/2OhGW0Z7s_4kprfM8_urlg#azure-alert-service-cloud-mgt "Configure the Microsoft Azure Alert service to auto-update the Configuration Management Database (CMDB) without waiting for the next scheduled Cloud Discovery to run.")
* [Configure the Google Cloud's Operations Suite Logging service to auto-update the CMDB](https://servicenow-prod.fluidtopics.net/n1rOTsbpCJ8SnFN66q~FMw "You can activate the Google Cloud Logging (formerly Stackdriver Logging) service to auto-update Configuration Management Database (CMDB) configuration items (CI) data whenever Google Cloud Connector or your Google account makes a life-cycle state or configuration change to a Google Cloud Platform (GCP) resource. As a result, the CI data in the CMDB is updated without having to wait for Discovery to run.")
{#tag-governance-real-time-updates__ul_ltg_x33_gqb}

Process cloud events related to changes in tags and execute tag audits on the events in real time.

Unlike regular tag audits, where the audit is performed on all CIs in the CMDB that the tag policy applies to, tag events are processed per CI. Based on the prerequisites, tag event processing occurs on events that are identified with a tag change. The impacted
CI is identified and, if the associated policy is applicable to the CI, the tag policy is run on the identified CI.

If the Run on cloud events check box is selected during policy creation, the policy is selected to run an audit on tag change events. If the check box is cleared, the audit is not run on the CI even if
there are tag change cloud events.

View the change type that applies to the tag (the change that triggered the audit) in the Tag Change Log \[sn_itom_tag_change_log\] table. The records in the table are stored for 90 days by default. The change log records appear
whether a remediation run or an event triggered the change on the CI. You can also view tags that were added or updated as part of the change.

## Optimizing performance {#tag-governance-real-time-updates__section_y1k_tnj_hcc}

High event inflow or a large number of tag policies can decrease performance. You can modify the following system properties to ensure acceptable performance:

* \[sn_itom_tag.azure_window_size\] - This system property is configurable (in minutes).
* \[sn_itom_tag.max_audit_lag_ratio\] - Specify the lag between tag audits that are already running, before the audit triggers on the records ready for audit.
* \[sn_itom_tag.policy_batch_size\] - Batch size on which the tag audit is run.
* \[sn_itom_tag.event_batch_size\] - Event batch size to be processed.
{#tag-governance-real-time-updates__ul_q5c_ght_cqb}