This page shows you how to resolve issues with Cloud Monitoring.
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.
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.
For guidance with issues that might arise when viewing collected metrics, see Troubleshooting metrics.
For guidance with issues that might arise when you use Cloud Monitoring Workspaces, see Troubleshooting workspaces.