[[["容易理解","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-04 (世界標準時間)。"],[],[],null,["# Troubleshoot\n\nThis page shows you how to resolve issues with Cloud Monitoring.\n\nUnable to select project with a billing alerting policy\n-------------------------------------------------------\n\nYou are creating a budget and have selected the option\n**Link Monitoring email notification channels to this budget** .\nYou expect to be able to select the Google Cloud project that contains the\nnotification channels by using the *arrow_drop_down* **Menu** of the\n**Select workspace** dialog. However, the project that you want to use isn't\nlisted.\n\nThe cause of this failure is that the project you want to select has\na *virtual* [metrics scope](/monitoring/settings#concept-scope). In\ngeneral, whether a metrics scope is virtual or instantiated has no\nimpact to usability; however, only projects with\nan instantiated metrics scope are listed in this dialog.\n\nOur engineering team is working to resolve this issue.\n\nTo have your project listed in the **Select workspace** dialog,\ndo the following:\n\n1. Convert the virtual metrics scope to an instantiated metrics scope. For detailed steps, see [Instantiate a metrics scope](#instantiate).\n2. Restart the create budget process.\n\n### Instantiate a metrics scope\n\nAssume that `MyNotificationsProject` contains the notification channels that\nyou want to use in the budget. To instantiate the metrics scope for this\nproject, you can add a second project as a monitored project. In the following\nsteps, the second project is named `TestProject`. After the metrics scope\nis instantiated, you can remove `TestProject` from the list of monitored\nprojects.\n\nTo ensure this project has an instantiated\nmetrics scope, do the following:\n\n1. Create a second project. In this example, the name of this project is\n `TestProject`.\n\n You can use an existing project as the second project; however, you\n can't use the project named `MyNotificationsProject`.\n2. Select `MyNotificationsProject` with the Google Cloud console project picker.\n\n3. Go to **Monitoring** and then select **Settings**.\n\n4. Click **Add GCP Projects**.\n\n5. In the table, check `TestProject`, and then click **Add projects**.\n\n When these steps are complete, `TestProject` is listed as a monitored\n project of `MyNotificationsProject`. This action forces the\n metrics scope of `MyNotificationsProject` to be instantiated.\n6. After the metrics scope is instantiated, you can remove `TestProject`\n from the list of monitored projects if desired. To remove `TestProject`\n from the list of monitored projects, in the **GCP Projects** table,\n check `TestProject` and then click **Remove projects**.\n\n7. If you created a second project in the first step, then you can now\n delete that project.\n\nCan't add a project to a metrics scope\n--------------------------------------\n\nYou attempt to add a project to a metrics scope, but the attempt fails.\n\nTo resolve this failure, try the following:\n\n- Make sure that you have the required permissions on the scoping project\n and on the project being added to the metrics scope.\n\n For information about these permissions, see the \"Before you begin\" section\n of [Configure a metrics scope](/monitoring/settings/multiple-projects).\n- Make sure that quota is available.\n\n By default, a metrics scope can include\n 375 Google Cloud projects. However, you can request\n an increase of the \"Monitored Projects / Monitoring Metrics Scope\" quota.\n For more information, see\n [Request a quota adjustment](/docs/quotas/view-manage#requesting_higher_quota).\n- Make sure that the project being added to the metrics scope is\n eligible.\n\n The metrics scope of a management project can only list child\n projects in the folder associated with the management project. To learn\n more about management projects, see\n [App Hub](/app-hub/docs/overview).\n\nMerge button isn't visible\n--------------------------\n\nThe **Merge** and **Move** buttons have been removed because this functionality\nisn't required now that Monitoring Workspaces have been\nreplaced with [metrics scopes](/monitoring/settings#concept-scope).\nWith the Workspace data model, the merge functionality was required because\na Google Cloud project could only be in a single Workspace. If you wanted\nto change which Workspace could view a project's metrics, you had to use the\nmerge option. With the metrics scope data model, this functionality\nisn't required because a Google Cloud project can be included in\nmultiple metrics scopes.\n\nFor information about how to view metrics for multiple projects, see\n[Configure a metrics scope for multiple projects](/monitoring/settings/multiple-projects).\n\nAWS logs aren't accessible.\n---------------------------\n\nTo access logs for your AWS account, use Cloud Logging with your\n[AWS hosting project](/logging/docs/agent/logging/authorization#before_you_begin) selected.\n\nAWS metrics are missing.\n------------------------\n\nAWS account metrics are stored in the Google Cloud project being used as the\n[AWS hosting project](/monitoring/agent/monitoring/authorization#before_you_begin). For this project to receive\nmetrics or logs, it must be a monitored project:\n\n- If you've removed an AWS hosting project from a Workspace,\n and as a result that AWS hosting project is\n no longer a monitored project, then new metric and log ingestion\n stops immediately.\n\n- If you've removed an AWS hosting project from a metrics scope,\n and as a result that AWS hosting project is\n no longer a monitored project, then new metric and log ingestion\n stops after 2 hours.\n\nUnable to access Cloud Monitoring.\n----------------------------------\n\nIf you aren't able to access Cloud Monitoring, then either you don't have a\nrole that lets you view monitoring data or the Google Cloud project hasn't been\nconfigured for Cloud Monitoring. For more information about the required\npermissions and roles, see\n[Control access with Identity and Access Management](/monitoring/access-control).\n\nProject resources are missing from Monitoring.\n----------------------------------------------\n\nIf you add or remove resources, such as VM instances, and then immediately go to\nMonitoring to view your resources, your recent changes aren't\nconsistent with the listed resources.\n\nTo resolve this issue, wait at least 10 minutes for Monitoring\nto discover the change in resources.\n\nServices are missing from Monitoring.\n-------------------------------------\n\nIf you start a new service and then immediately go to Monitoring\nto view that service, it isn't listed in the list of services.\n\nTo resolve this issue, wait at least one hour for the new service to be\ndiscovered.\n\nTroubleshoot the Cloud Monitoring agent\n---------------------------------------\n\nFor guidance on diagnosing problems with the installation or running of\nthe Cloud Monitoring agent, see\n[Troubleshoot agent installation](/monitoring/agent/troubleshooting).\n\nTroubleshoot alerting policies\n------------------------------\n\nFor information about how alerting policies are affected by the\nmetrics and resources monitored by conditions,\nthe duration window for conditions, and when incidents are created, see\n[Behavior of metric-based alerting policies](/monitoring/alerts/concepts-indepth).\n\nFor guidance with issues that might arise with specific alerting policies, see\n[Troubleshoot alerting policies](/monitoring/alerts/troubleshooting-alerts).\n\nTroubleshoot charts and metrics\n-------------------------------\n\nFor guidance with issues specific to charts or dashboards, see\n[Troubleshoot charts and dashboards](/monitoring/charts/troubleshooting-charts).\n\nTroubleshoot using the Cloud Monitoring API\n-------------------------------------------\n\nFor guidance with issues that might arise when you use the\nCloud Monitoring API v3, see\n[Troubleshoot the Cloud Monitoring API](/monitoring/api/troubleshooting).\n\nTroubleshoot uptime checks\n--------------------------\n\nFor guidance with issues specific to uptime checks, see\n[Troubleshoot uptime checks](/monitoring/uptime-checks/troubleshoot)."]]
