Troubleshooting

This page shows you how to resolve issues with Cloud Monitoring.

Unable to select project with a billing alert

You are creating a budget and have selected the option Link Monitoring email notification channels to this budget. You expect to be able to select the Google Cloud project that contains the notification channels by using the Menu of the Select workspace dialog. However, the project that you want to use isn't listed.

The cause of this failure is that the project you want to select has a virtual metrics scope. In general, whether a metrics scope is virtual or instantiated has no impact to usability; however, only projects with an instantiated metrics scope are listed in this dialog.

Our engineering team is working to resolve this issue.

To have your project listed in the Select workspace dialog, do the following:

  1. Convert the virtual metrics scope to an instantiated metrics scope. For detailed steps, see Instantiate a metrics scope.
  2. Restart the create budget process.

Instantiate a metrics scope

Assume that MyNotificationsProject contains the notification channels that you want to use in the budget. To instantiate the metrics scope for this project, you can add a second project as a monitored project. In the following steps, the second project is named TestProject. After the metrics scope is instantiated, you can remove TestProject from the list of monitored projects.

To ensure this project has an instantiated metrics scope, do the following:

  1. Create a second project. In this example, the name of this project is TestProject.

    You can use an existing project as the second project; however, you can't use the project named MyNotificationsProject.

  2. Select MyNotificationsProject with the Cloud Console project picker.

  3. Go to Monitoring and then select Settings.

  4. Click Add GCP Projects.

  5. In the table, check TestProject, and then click Add projects.

    When these steps are complete, TestProject is listed as a monitored project of MyNotificationsProject. This action forces the metrics scope of MyNotificationsProject to be instantiated.

  6. After the metrics scope is instantiated, you can remove TestProject from the list of monitored projects if desired. To remove TestProject from the list of monitored projects, in the GCP Projects table, check TestProject and then click Remove projects.

  7. If you created a second project in the first step, then you can now delete that project.

Merge button isn't visible

The Merge and Move buttons have been removed because this functionality isn't required now that Monitoring Workspaces have been replaced with metrics scopes. With the Workspace data model, the merge functionality was required because a Google Cloud project could only be in a single Workspace. If you wanted to change which Workspace could view a project's metrics, you had to use the merge option. With the metrics scope data model, this functionality isn't required because a Google Cloud project can be included in multiple metrics scopes.

For information about how to view metrics for multiple projects, see Viewing metrics for multiple projects.

AWS logs aren't accessible.

To access logs for your AWS account, use Cloud Logging with your AWS connector project selected.

AWS logs and metrics are missing.

AWS account metrics are stored in its AWS connector project. For this project to receive metrics or logs, it must be a monitored project:

  • If you've remove an AWS connector project from a Workspace, and as a result that AWS connector project is no longer a monitored project, then new metric and log ingestion stops immediately.

  • If you've remove an AWS connector project from a metrics scope, and as a result that AWS connector project is no longer a monitored project, then new metric and log ingestion stops after 2 hours.

If this is a new configuration, ensure that you've added to the Amazon IAM role the trust relationship for the AWS connector project. For more information on configuring the Amazon IAM role, see Configuring Google Cloud to read your AWS account metrics .

Unable to access Cloud Monitoring.

If you aren't able to access Cloud Monitoring, then either you don't have a role that lets you view monitoring data or the Google Cloud project hasn't been configured for Cloud Monitoring. For more information about the required permissions and roles, see [Authorization][authorization].

Project resources are missing from Monitoring.

If you add or remove resources, such as VM instances, and then immediately go to Monitoring to view your resources, your recent changes aren't consistent with the listed resources.

To resolve this issue, wait at least 10 minutes for Monitoring to discover the change in resources.

Services are missing from Monitoring.

If you start a new service and then immediately go to Monitoring to view that service, it isn't listed in the list of services.

To resolve this issue, wait at least one hour for the new service to be discovered.

Troubleshooting the Cloud Monitoring agent

For guidance on diagnosing problems with the installation or running of the Cloud Monitoring agent, see Troubleshooting agent installation.

Troubleshooting the Cloud Monitoring API

For guidance with issues that might arise when you use the Cloud Monitoring API v3, see Troubleshooting the Cloud Monitoring API.

Troubleshooting alerting policies

For information about how alerting policies are affected by the metrics and resources monitored by conditions, the duration window for conditions, and when incidents are created, see Alerting behavior.

For guidance with issues that might arise with specific alerting policies, see Troubleshooting alerting policies.

Troubleshooting charts and metrics

For guidance with issues specific to charts or dashboards, see Troubleshooting charts and dashboards.

For guidance with issues that might arise when viewing collected metrics, see Troubleshooting metrics.