[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-29。"],[],[],null,["# Configure a metrics scope\n\nThis document describes how to use the Google Cloud console to configure a\nGoogle Cloud project so that you can chart and monitor time-series data stored in\nmultiple projects. This document is\nintended for developers and system administrators who need to manage\ntime-series data for services and resources that are\nassociated with different projects.\n\nFor information about configuring a Google Cloud project\nprogrammatically, see\n[Configure a metrics scope by using the API](/monitoring/settings/manage-api).\n\nThe metrics scope of a Google Cloud project determines the\ntime-series data that the project can chart or monitor with alerting policies.\n\nApp Hub applications and metrics scopes\n---------------------------------------\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nYou manage the metrics scope for [App Hub](/app-hub/docs/overview)\nhost projects. You can manage this scope either by using the\n[Google Cloud console](/monitoring/settings/multiple-projects) or the\n[Cloud Monitoring API](/monitoring/settings/manage-api).\n\nGoogle Cloud manages the metrics scope for app-enabled folders, unless\nadding a project to the metrics scope fails due to exhaustion of the\nmetrics scope quota. In this case, you can request a quota increase and\nthen manually add projects to the metrics scope of the\nmanagement project for the app-enabled folder. To learn more, see\n[Metrics scopes for app-enabled folders](/monitoring/settings/metrics-scope-app-enabled-folders).\n\nBefore you begin\n----------------\n\n- If you aren't familiar with the terms *metrics scope* and *scoping project* , then see [Metrics scopes overview](/monitoring/settings).\n\n\u003c!-- --\u003e\n\n-\n\n To get the permissions that\n you need to configure a metrics scope,\n\n ask your administrator to grant you the\n\n\n [Monitoring Admin](/iam/docs/roles-permissions/monitoring#monitoring.admin) (`roles/monitoring.admin`)\n IAM role on the scoping project and on each project\n that you want to add to, or remove from, the metrics scope.\n\n\n For more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\n You might also be able to get\n the required permissions through [custom\n roles](/iam/docs/creating-custom-roles) or other [predefined\n roles](/iam/docs/roles-overview#predefined).\n- If you use [VPC Service Controls](/vpc-service-controls/docs/overview), then you need to consider\n the order in which you configure a metrics scope and\n your VPC perimeters. Cloud Monitoring performs the VPC perimeter check\n when a project is *added* to a metrics scope:\n\n - When you create the VPC perimeter first and then try to add a\n project to\n the metrics scope, the perimeter validation process runs. This\n process verifies that the added container is in the same perimeter as the\n scoping project, or that it is connected to the\n scoping project by a [perimeter bridge](/vpc-service-controls/docs/share-across-perimeters).\n If the perimeter validation fails, then the addition of the\n project to the metrics scope also fails.\n\n - When you configure the metrics scope first and then\n create your perimeters, the perimeter validation process doesn't run.\n This approach lets you access time-series data for projects\n that are in different perimeters.\n\n- If you configure IAM roles or grant access to projects,\n then consider the implications of permissions on a project\n whose metrics scope includes projects other than the\n scoping project.\n A role that grants read permission to Monitoring on the\n scoping project lets the principal view charts and alerting policies\n that might display data that is stored by a project included\n in the metrics scope.\n\nAdd projects to a metrics scope\n-------------------------------\n\nTo add projects to a metrics scope, do the following:\n\n1. In the Google Cloud console, go to the\n *settings* **Settings** page:\n\n [Go to **Settings**](https://console.cloud.google.com/monitoring/settings)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. In the Google Cloud console, select your Google Cloud project. For [App Hub](/app-hub/docs/overview) host project configurations, select the host project.\n3. Select **Metric Scope**.\n\n The **Metric Scope** tab lists the resources monitored by the current\n Google Cloud project. It also lists the Google Cloud projects whose\n metrics scope includes the current Google Cloud project.\n4. To add Google Cloud projects to the metrics scope:\n\n 1. In the **Google Cloud Projects** pane, click **Add Projects**.\n 2. In the **Add Google Cloud projects** dialog, click **Select Projects** ,\n and then make your selections. To save your changes, click\n **Add Projects**.\n\n \u003cbr /\u003e\n\n You are returned to the **Settings** page, and the table on that page\n is updated to list your selections. If you want to remove a\n Google Cloud project from the list,\n click *cancel* **Remove project**.\n\n\n After you add projects to a metrics scope, it takes about 60 seconds for\n changes to propagate through all Monitoring systems.\n\n Before you create a chart or alerting policy, wait at least 60 seconds.\n You might need to refresh the Google Cloud console page for the new metrics to be visible.\n\n The metrics scope of your selected project has been updated to include\n the Google Cloud projects you selected.\n\nRemove projects from a metrics scope\n------------------------------------\n\nYou might want to remove projects from a metrics scope to improve\nperformance or to free up quota so that you can add a different project.\nFor example, by default, a metrics scope can include\n375 Google Cloud projects. If you've exhausted this quota,\nthen you might remove one project so that you can add another.\n\nAfter you remove a project from a metrics scope, the time-series\ndata stored in that project can't be charted or monitored by the\nscoping project. Removing a project from a metrics scope doesn't\nchange the configuration of charts,\ndashboards, alerting policies, uptime checks, or groups that you defined.\nHowever, the time series displayed on charts and the time series monitored by\nalerting policies might change.\n\nTo remove projects from a metrics scope, do the following:\n\n1. In the Google Cloud console, go to the\n *settings* **Settings** page:\n\n [Go to **Settings**](https://console.cloud.google.com/monitoring/settings)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. In the Google Cloud console, select your Google Cloud project. For [App Hub](/app-hub/docs/overview) host project configurations, select the host project.\n3. Select **Metric Scope**.\n4. In the **Google Cloud Projects** pane, select the projects that you want to remove, click **Remove project**, and then complete the confirmation dialog.\n\nList projects in a metrics scope\n--------------------------------\n\nTo list the resources in a metrics scope, do the following:\n\n1. In the Google Cloud console, go to the\n *settings* **Settings** page:\n\n [Go to **Settings**](https://console.cloud.google.com/monitoring/settings)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. In the Google Cloud console, select your Google Cloud project. For [App Hub](/app-hub/docs/overview) host project configurations, select the host project.\n3. Select **Metric Scope**.\n\n The **Metric Scope** tab lists the resources monitored by the current\n Google Cloud project. It also lists the Google Cloud projects whose\n metrics scope includes the current Google Cloud project.\n\nRequest a quota increase\n------------------------\n\nBy default, a metrics scope can include\n375 Google Cloud projects. However, you can request\nan increase of the \"Monitored Projects / Monitoring Metrics Scope\" quota.\nIncreasing your quota beyond the default value of\n375 Google Cloud projects might cause performance issues.\n\nFor instructions about how to request a quota increase, see\n[Request a quota adjustment](/docs/quotas/view-manage#requesting_higher_quota).\n\nSelect a different metrics scope\n--------------------------------\n\nThe project selected in the Google Cloud console project picker is the\nscoping project of the current metrics scope. There is a one-to-one\nrelationship between a scoping project and a metrics scope.\n\nTo select a different metrics scope, select a different project with the\nGoogle Cloud console project picker.\n\nWhat's next\n-----------\n\n- [Quotas and limits](/monitoring/quotas)"]]
