Troubleshooting Cloud Network Insights

Preview

This product is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products are available "as is" and might have limited support. For more information, see the launch stage descriptions.

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 by doing one of the following:

1. Docker: Run docker ps and check that containers ending in sequencer_1 and talos-001_1 are Up.
2. Kubernetes: Run kubectl --namespace appneta get pods to verify pods are Running.

For troubleshooting information, see the following AppNeta resources:

• View the Monitoring Point Status
• Docker Troubleshooting Connectivity Quick Reference
• Helm Troubleshooting Connectivity Quick Reference

Virtual machine Monitoring Points aren't active

For VMware and KVM, open the Web Admin interface to diagnose the issue.

1. Navigate to https://MP_IP_ADDRESS in a web browser.

2. Sign in:

   1. Username: admin
   2. Default Password: The Monitoring Point's MAC Address (found in the hypervisor settings). Enter it in UPPERCASE with no colons (for example, 00505681450A)
      1. KVM Monitoring Point Admin Credentials.
      2. VMWare Monitoring Point Admin Credentials.

3. Check Status Indicators:

   1. Monitoring Point Connected: Must be Yes.
   2. NTP Synchronized: Must be Yes. If No, ensure outbound UDP port 123 is allowed.
   3. Network State: Ensure eth0 is Up.

For troubleshooting information, see the following AppNeta resources:

• KVM Troubleshooting Connectivity Quick Reference.
• VMWare Troubleshooting Connectivity Quick Reference.

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.