[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["# Data regionality for Cloud Monitoring\n\nThis page describes the storage policies for data that is used by\nCloud Monitoring. Cloud Monitoring is a [global product](/about/locations#global-products)\nand its services are available with no dependence on location.\n\nStorage of time-series data\n---------------------------\n\nGoogle agents, client-side code using libraries like OpenTelemetry,\nand third-party sources such as [BindPlane](/stackdriver/bindplane),\nwrite time series by using the Cloud Monitoring API. Google services also write\ntime series, but they use internal mechanisms.\n\nTo store a time series in a specific [region](/compute/docs/regions-zones),\nthe monitored resource against which the time series is written must have\none of the following labels and the value of the label must be valid:\n\n- `location`\n- `zone`\n- `region`\n\nA time series is discarded when\nthe monitored resource against which the time series is written has one of\nthe previous labels and the value of the label isn't recognized or isn't\nspecified.\n\nThe storage location of a time series is unspecified when\nthe monitored resource against which the time series is written doesn't have\none of the previous labels.\n\nTo view a list of all monitored resources and their labels, see\n[Monitored resource types](/monitoring/api/resources). For those monitored resources that\ncontain a location label, the entry indicates the valid values for that label.\n\nThe [resource locations constraint](/resource-manager/docs/organization-policy/defining-locations)\ndoesn't apply to time series.\n\n### Data written by Google Cloud products\n\nGoogle Cloud products deployable by zone or by region\nstore any time series that they generate in the same region\nto which they are deployed. For a list of these products, see\n[Products available by location](/about/locations#products-available-by-location).\n\nFor all other Google products, the storage location of any time series\nthat the product generates is unspecified. For a list of these products, see\n[Global products](/about/locations#global-products).\n\n### Custom metrics\n\nTime series for custom metrics follow the location rules described in\n[Storage of time-series data](#time-series-data). Examples of custom metrics\ninclude metrics you create from your applications\nby using libraries such as OpenCensus and OpenTelemetry.\n\nNot all monitored resource types that are available for custom metrics\nhave a location label.\nFor example, the [`global`](/monitoring/api/resources#tag_global) resource only has a label for\nthe project identifier. For a list of the monitored resource types available\nfor custom metrics,\nsee [Monitored resources for custom metrics](/monitoring/custom-metrics/creating-metrics#custom-metric-resources).\n\nProcessing of time-series data\n------------------------------\n\nThe physical location where time-series data are processed when such data\nare queried depend on many factors including the storage location of the data,\nquery semantics, networking, and others. In general, there is no guarantee\nthat time series are always processed in the location where\nthey are physically stored.\n\nAlert notifications\n-------------------\n\nWhen Monitoring sends a notification of an alert,\nthat information might pass through third-party providers that don't support\ndata localization. For example, customers can configure an alert notification\nto be delivered to any email address, to a Slack channel, or through SMS.\nFor details on all available channel types, see\n[Create and manage notification channels](/monitoring/support/notification-options).\n\nUptime checks and synthetic monitors\n------------------------------------\n\nCustomers who have set up\n[Assured Workloads](/assured-workloads) because they have\ndata-residency or [Impact Level 4 (IL4)](/security/compliance/disa)\nrequirements, shouldn't use\n[uptime checks or synthetic monitors](/monitoring/uptime-checks/introduction)."]]
