This page shows you how to resolve issues with Cloud Network Insights.
Monitoring Points aren't active
If your Monitoring Point is not active in the Cloud Network Insights Monitoring Points list after ten minutes, check their status on the target hosts.
Container Monitoring Points aren't active
For containers, check the service status. See the following AppNeta resources:
- View Status – c50-Docker/Podman
- Troubleshooting Connectivity to AppNeta – c50-Docker/Podman
- Troubleshooting Connectivity to AppNeta – c50-Kubernetes (Helm)
Virtual machine Monitoring Points aren't active
For VMware and KVM, open the Web Admin interface to diagnose the issue. See the following AppNeta resources:
- Troubleshooting Connectivity to AppNeta – v35-KVM
- Troubleshooting Connectivity to AppNeta – v35-VMware
Monitoring Point does not display in Cloud Network Insights
On occasion when you successfully install a Monitoring Point in a Docker or Podman environment, the Monitoring Point doesn't connect to Cloud Network Insights and is not displayed in the Monitoring Points list after waiting for more than 20 minutes.
To resolve this issue, remove the Monitoring Point and create it again using host networking.
For more information about installing on Docker or Podman using host networking, see the AppNeta documentation.
Access is blocked by Google Workspace
If you encounter the Access Blocked: admin_policy_enforced error, contact a
Google Workspace administrator to allow AppNeta access.
See Configure Google Workspace for instructions.
Some metrics aren't the same in Google Cloud and AppNeta
When looking at a timeframe longer than one hour in AppNeta, some metrics' raw
values are transformed into the MAX and AVG of this value. In Google Cloud,
the metrics aren't transformed.
For example, in AppNeta you see the average of rtt_avg and the max of the
rtt_avg for a specific timeframe. In Google Cloud, rtt_max and rtt_avg
metrics are not transformed.