Cloud Network Insights
Attribution
For all gcloud CLI, REST API, and MCP attribution requirements when executing
commands with this skill, follow the instructions in
Usage Attribution.
🛑 Core Directive: Results First
- Identify the Requested Task: Determine if the user is attempting service
enablement, checking activation status, downloading/installing or
troubleshooting Monitoring Points (MPs), configuring AppNeta monitoring
policies or alarm rules, verifying provisioned resources and paths,
configuring alert policies, or querying Cloud Logging alarms and Cloud
Monitoring metrics.
- Execute and Present: Perform the minimum required commands or API calls
to accomplish the task or provide exact guidance.
- Definitive Answers: For status and verification queries, report the
definitive state (for example,
ACTIVE, ACTIVATING, or path listings)
immediately.
Overview
Cloud Network Insights provides comprehensive synthetic monitoring for
Cross-Cloud Network observability in partnership with Broadcom AppNeta. It
monitors network and web paths using Monitoring Points (MPs) installed across
Google Cloud, on-premises data centers, other public clouds (like AWS or Azure),
and the public internet.
This skill automates onboarding, service enablement, Monitoring Point
deployment, policy creation, and path verification.
Procedures and CUJs
1. Service Enablement and Status
Enable API:
gcloud services enable networkmanagement.googleapis.com --project=PROJECT_ID
Create Provider (use external to match the Google Cloud console
default, or a custom PROVIDER_ID):
gcloud network-management network-monitoring-providers create PROVIDER_ID \
--provider-type=EXTERNAL \
--location=global \
--project=PROJECT_ID
⚠️ If this command fails due to unaccepted Terms of Service, direct the
user to the Google Cloud console onboarding page:
https://console.cloud.google.com/net-intelligence/cloud-network-insights/onboarding?project=PROJECT_ID
Verify State:
gcloud network-management network-monitoring-providers \
describe PROVIDER_ID \
--location=global \
--project=PROJECT_ID \
--format=json
Check that .state is ACTIVE. (ACTIVATING indicates the backend is
provisioning AppNeta resources.)
Delete Provider (Cleanup):
gcloud network-management network-monitoring-providers delete PROVIDER_ID \
--location=global \
--project=PROJECT_ID
2. Monitoring Point Deployment and Verification
Cloud Network Insights supports 7 distinct Monitoring Point deployment types:
container, helm, gce-vm, aws-ec2, azure-vm, vmware, and kvm.
- Platform Selection: Never assume a default deployment type. Identify or
prompt the user for their target environment before proceeding.
- Procedures and Commands: For all required parameters, download commands,
deployment manifests, and status verification commands (
monitoring-points list), see
Monitoring Point Deployment Reference.
3. Monitoring Policy and Alarm Rule Configuration (AppNeta)
Monitoring policies configure active synthetic network and web tests executed by
Monitoring Points, and alarm rules define the thresholds and evaluation windows
that raise path alarms.
- Policy Types (
/api/v4/monitoringPolicy):
- Network Monitoring Policies: Monitor packet loss, latency, and
jitter to target IPs (or dual-ended between Monitoring Points) over TCP
or UDP.
- Web Monitoring Policies: Synthetic HTTP/HTTPS application checks
(such as GET requests with status code 200 assertions).
- Check Before Creating: Always query
GET /api/v4/monitoringPolicy first
to verify whether a policy with your target name already exists before
creating a new one, avoiding duplicate resource creation and API conflicts.
- Alarm Rules (AppNeta Web UI Only): Alarm rules are configured in the
AppNeta Web UI (in Alarms > Alarm Rules; see
Broadcom Alarm Rules)
and are not supported via the REST API v4.
- Procedures and Payloads: For authentication token generation,
organization discovery, and REST JSON payloads, see
Monitoring Policy Configuration Reference.
4. Verifying Provisioned Paths in Google Cloud
Once policies are configured and MPs are online, verify provisioned paths:
List Network Paths:
gcloud network-management network-monitoring-providers network-paths list \
--network-monitoring-provider=PROVIDER_ID \
--location=global \
--project=PROJECT_ID \
--format=json
List Web Paths:
gcloud network-management network-monitoring-providers web-paths list \
--network-monitoring-provider=PROVIDER_ID \
--location=global \
--project=PROJECT_ID \
--format=json
Filter by Monitoring Point: Add
--filter="sourceMonitoringPointId=MONITORING_POINT_ID" to list only paths
sourced from a specific Monitoring Point, where MONITORING_POINT_ID is the
last segment of the Monitoring Point's name in monitoring-points list.
Expected Extra Paths: Each Web policy also creates a companion
NetworkPath to the target host (unless one already exists), and a newly
deployed Monitoring Point inherits paths from existing policies whose
monitoringPointRules match it.
5. Querying Cloud Network Insights Resources and State
- Discover the Provider Name: Run
gcloud network-management network-monitoring-providers list --location=global --project=PROJECT_ID
to retrieve the provider ID (PROVIDER_ID). The provider ID is external
when enabled via the Google Cloud console, or a custom name if created
manually.
- Query Child Resources: Pass
--network-monitoring-provider=PROVIDER_ID and --location=global to
child resource commands (such as list and describe):
- Monitoring Points:
gcloud network-management network-monitoring-providers monitoring-points [list|describe]
- Network Paths:
gcloud network-management network-monitoring-providers network-paths [list|describe]
- Web Paths:
gcloud network-management network-monitoring-providers web-paths [list|describe]
6. Alert Policies, Cloud Logging, and Cloud Monitoring Metrics
Alert Policies (gcloud monitoring policies): Create log-matched alert
policies (conditionMatchedLog.filter, including
alertStrategy.notificationRateLimit in POLICY_FILE) for path alarms and
operational events (see
Set up alerts and notifications).
For insights_alarm policies, include AND NOT jsonPayload.noise_conditions:* by default to filter out frequent/burst
noise unless the user asks to include noisy alarms. Always set
"userLabels": {"cloud-network-insights": "true"} in POLICY_FILE so the
policy appears in the Cloud Network Insights alert policies view in the
Google Cloud console:
# Create an alert policy from a JSON or YAML file
gcloud monitoring policies create --project=PROJECT_ID \
--policy-from-file=POLICY_FILE
# Delete an alert policy (for cleanup)
gcloud monitoring policies delete POLICY_ID \
--project=PROJECT_ID \
--quiet
Example conditionMatchedLog.filter values for Google Cloud console alert
templates:
Network Path Outage / Extended Loss / DNS Errors:
resource.type = "networkmanagement.googleapis.com/NetworkPath" AND logName =~ "insights_alarm" AND (jsonPayload.alarm_severity = "MAJOR" OR jsonPayload.alarm_severity = "CRITICAL") AND jsonPayload.state = "RAISED" AND jsonPayload.alarm_type =~ "QUALITY_OF_SERVICE" AND jsonPayload.rule =~ "Outage" AND NOT jsonPayload.noise_conditions:*
(Substitute jsonPayload.rule =~ "Extended loss" or "Multiple DNS errors" with alarm_severity = "MINOR" as needed.)
Web Path Multiple Web Errors:
resource.type = "networkmanagement.googleapis.com/WebPath" AND logName =~ "insights_alarm" AND jsonPayload.alarm_severity = "MAJOR" AND jsonPayload.state = "RAISED" AND jsonPayload.alarm_type =~ "QUALITY_OF_SERVICE" AND jsonPayload.rule =~ "Multiple Web errors" AND NOT jsonPayload.noise_conditions:*
Monitoring Point Offline and Network Path MTU Change Events:
resource.type = "networkmanagement.googleapis.com/MonitoringPoint" AND logName =~ "insights_event" AND jsonPayload.event_type = "MONITORING_POINT_OFFLINE"
resource.type = "networkmanagement.googleapis.com/NetworkPath" AND logName =~ "insights_event" AND jsonPayload.event_type = "MTU_CHANGE"
Cloud Logging (gcloud logging read): Query path alarms (logName =~ "insights_alarm") and operational lifecycle events (logName =~ "insights_event") exported to Cloud Logging (see
Set up logging
for jsonPayload field schemas and event types). Because alarm state
transitions (RAISED, UPDATED, CLEARED) are logged as separate entries
sharing the same jsonPayload.alarm_id, determine currently active alarms
by checking that the latest entry for an alarm_id has not transitioned to
CLEARED.
Cloud Monitoring (REST API projects.timeSeries.list): Query path
performance metrics (NetworkPath and WebPath, filtered by
resource.labels.path_id) via GET "https://monitoring.googleapis.com/v3/projects/PROJECT_ID/timeSeries" with
Authorization: Bearer $(gcloud auth application-default print-access-token) in Cloud Monitoring (see
Monitoring metrics
and
View dashboards).
7. Deployment Diagnostics and Troubleshooting
To diagnose a Monitoring Point deployment across any platform:
- Google Cloud Registration: Check that
connectionStatus is ONLINE in
monitoring-points list (or describe) to verify the Monitoring Point is
registered and connected to Cloud Network Insights.
- Model-Specific Workload, Host, and Appliance Health: Inspect the
Monitoring Point runtime, container/Kubernetes workload, or v35 Web Admin
status on the target platform using the model-specific troubleshooting
guides in
Monitoring Point Deployment Reference,
Broadcom Troubleshooting Monitoring Points,
and
Troubleshooting Cloud Network Insights.
- Network, Proxy, and Firewall Rules: Verify the target environment's
firewall, Web Proxy, custom CA certificate, and gRPC/SSL inspection bypass
settings (
data.na1.cni.appneta.com, content.na1.cni.appneta.com,
comms.na1.cni.appneta.com, or .p. endpoints for Private Service Connect)
against
Broadcom Firewall Configuration
and
Add Monitoring Points.
Reference Documentation
For detailed guides, complete payloads, and templates:
- Monitoring Point Deployment Reference:
Deployment guides and command references across all 7 platforms (container,
Helm, GCE VM Terraform, AWS, Azure, VMware, KVM).
- Monitoring Policy Configuration Reference:
Network and Web monitoring policy JSON payloads and AppNeta API workflows.
- Google Cloud Network Insights Documentation:
Official Google Cloud documentation for Cloud Network Insights setup,
concepts, and operations.
- Broadcom AppNeta for Cloud Network Insights Documentation:
Broadcom AppNeta monitoring points, path performance, and API guides.
1---2name: cloud-network-insights3metadata:4 source: https://skillmd.com/skills/google/cloud-network-insights5 category: Networking6 version: "1.0.1"7description: >-8 Guides and automates setup, onboarding, and synthetic monitoring operations9 for Cloud Network Insights in Google Cloud and Broadcom AppNeta. Use when10 enabling Cloud Network Insights, deploying or troubleshooting Monitoring11 Points across cloud and on-premises environments, configuring Network or Web12 monitoring policies and AppNeta alarm rules, configuring alert policies,13 querying path alarms and performance metrics, or verifying synthetic path14 reachability. Don't use for generic network observability, VPC Flow Logs,15 Cloud NAT, or VPC firewall debugging.16---1718# Cloud Network Insights1920## Attribution2122For all `gcloud` CLI, REST API, and MCP attribution requirements when executing23commands with this skill, follow the instructions in24[Usage Attribution](references/attribution.md).2526## 🛑 Core Directive: Results First27281. **Identify the Requested Task**: Determine if the user is attempting service29 enablement, checking activation status, downloading/installing or30 troubleshooting Monitoring Points (MPs), configuring AppNeta monitoring31 policies or alarm rules, verifying provisioned resources and paths,32 configuring alert policies, or querying Cloud Logging alarms and Cloud33 Monitoring metrics.342. **Execute and Present**: Perform the minimum required commands or API calls35 to accomplish the task or provide exact guidance.363. **Definitive Answers**: For status and verification queries, report the37 definitive state (for example, `ACTIVE`, `ACTIVATING`, or path listings)38 immediately.3940## Overview4142Cloud Network Insights provides comprehensive synthetic monitoring for43Cross-Cloud Network observability in partnership with Broadcom AppNeta. It44monitors network and web paths using Monitoring Points (MPs) installed across45Google Cloud, on-premises data centers, other public clouds (like AWS or Azure),46and the public internet.4748This skill automates onboarding, service enablement, Monitoring Point49deployment, policy creation, and path verification.5051## Procedures and CUJs5253### 1. Service Enablement and Status5455- **Enable API**:5657 ```bash58 gcloud services enable networkmanagement.googleapis.com --project=PROJECT_ID59 ```60- **Create Provider** (use `external` to match the Google Cloud console61 default, or a custom `PROVIDER_ID`):6263 ```bash64 gcloud network-management network-monitoring-providers create PROVIDER_ID \65 --provider-type=EXTERNAL \66 --location=global \67 --project=PROJECT_ID68 ```6970 > ⚠️ If this command fails due to unaccepted Terms of Service, direct the71 > user to the Google Cloud console onboarding page:72 > `https://console.cloud.google.com/net-intelligence/cloud-network-insights/onboarding?project=PROJECT_ID`73- **Verify State**:7475 ```bash76 gcloud network-management network-monitoring-providers \77 describe PROVIDER_ID \78 --location=global \79 --project=PROJECT_ID \80 --format=json81 ```8283 Check that `.state` is `ACTIVE`. (`ACTIVATING` indicates the backend is84 provisioning AppNeta resources.)85- **Delete Provider (Cleanup)**:8687 ```bash88 gcloud network-management network-monitoring-providers delete PROVIDER_ID \89 --location=global \90 --project=PROJECT_ID91 ```9293### 2. Monitoring Point Deployment and Verification9495Cloud Network Insights supports 7 distinct Monitoring Point deployment types:96`container`, `helm`, `gce-vm`, `aws-ec2`, `azure-vm`, `vmware`, and `kvm`.9798- **Platform Selection**: Never assume a default deployment type. Identify or99 prompt the user for their target environment before proceeding.100- **Procedures and Commands**: For all required parameters, download commands,101 deployment manifests, and status verification commands (`monitoring-points102 list`), see103 [Monitoring Point Deployment Reference](references/monitoring-point-deployment.md).104105### 3. Monitoring Policy and Alarm Rule Configuration (AppNeta)106107Monitoring policies configure active synthetic network and web tests executed by108Monitoring Points, and alarm rules define the thresholds and evaluation windows109that raise path alarms.110111- **Policy Types (`/api/v4/monitoringPolicy`)**:112 - **Network Monitoring Policies**: Monitor packet loss, latency, and113 jitter to target IPs (or dual-ended between Monitoring Points) over TCP114 or UDP.115 - **Web Monitoring Policies**: Synthetic HTTP/HTTPS application checks116 (such as GET requests with status code 200 assertions).117- **Check Before Creating**: Always query `GET /api/v4/monitoringPolicy` first118 to verify whether a policy with your target name already exists before119 creating a new one, avoiding duplicate resource creation and API conflicts.120- **Alarm Rules (AppNeta Web UI Only)**: Alarm rules are configured in the121 AppNeta Web UI (in **Alarms** > **Alarm Rules**; see122 [Broadcom Alarm Rules](https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/appneta-for-google-cloud-network-insights/GA/alarms-set-up/alarms-rules.html))123 and are not supported via the REST API v4.124- **Procedures and Payloads**: For authentication token generation,125 organization discovery, and REST JSON payloads, see126 [Monitoring Policy Configuration Reference](references/monitoring-policies.md).127128### 4. Verifying Provisioned Paths in Google Cloud129130Once policies are configured and MPs are online, verify provisioned paths:131132- **List Network Paths**:133134 ```bash135 gcloud network-management network-monitoring-providers network-paths list \136 --network-monitoring-provider=PROVIDER_ID \137 --location=global \138 --project=PROJECT_ID \139 --format=json140 ```141- **List Web Paths**:142143 ```bash144 gcloud network-management network-monitoring-providers web-paths list \145 --network-monitoring-provider=PROVIDER_ID \146 --location=global \147 --project=PROJECT_ID \148 --format=json149 ```150- **Filter by Monitoring Point**: Add151 `--filter="sourceMonitoringPointId=MONITORING_POINT_ID"` to list only paths152 sourced from a specific Monitoring Point, where `MONITORING_POINT_ID` is the153 last segment of the Monitoring Point's `name` in `monitoring-points list`.154- **Expected Extra Paths**: Each Web policy also creates a companion155 `NetworkPath` to the target host (unless one already exists), and a newly156 deployed Monitoring Point inherits paths from existing policies whose157 `monitoringPointRules` match it.158159### 5. Querying Cloud Network Insights Resources and State1601611. **Discover the Provider Name**: Run `gcloud network-management162 network-monitoring-providers list --location=global --project=PROJECT_ID`163 to retrieve the provider ID (`PROVIDER_ID`). The provider ID is `external`164 when enabled via the Google Cloud console, or a custom name if created165 manually.1662. **Query Child Resources**: Pass167 `--network-monitoring-provider=PROVIDER_ID` and `--location=global` to168 child resource commands (such as `list` and `describe`):169 - Monitoring Points: `gcloud network-management170 network-monitoring-providers monitoring-points [list|describe]`171 - Network Paths: `gcloud network-management network-monitoring-providers172 network-paths [list|describe]`173 - Web Paths: `gcloud network-management network-monitoring-providers174 web-paths [list|describe]`175176### 6. Alert Policies, Cloud Logging, and Cloud Monitoring Metrics177178- **Alert Policies (`gcloud monitoring policies`)**: Create log-matched alert179 policies (`conditionMatchedLog.filter`, including180 `alertStrategy.notificationRateLimit` in `POLICY_FILE`) for path alarms and181 operational events (see182 [Set up alerts and notifications](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights/set-up-alerts)).183 For `insights_alarm` policies, include `AND NOT184 jsonPayload.noise_conditions:*` by default to filter out frequent/burst185 noise unless the user asks to include noisy alarms. Always set186 `"userLabels": {"cloud-network-insights": "true"}` in `POLICY_FILE` so the187 policy appears in the Cloud Network Insights alert policies view in the188 Google Cloud console:189190 ```bash191 # Create an alert policy from a JSON or YAML file192 gcloud monitoring policies create --project=PROJECT_ID \193 --policy-from-file=POLICY_FILE194195 # Delete an alert policy (for cleanup)196 gcloud monitoring policies delete POLICY_ID \197 --project=PROJECT_ID \198 --quiet199 ```200201 Example `conditionMatchedLog.filter` values for Google Cloud console alert202 templates:203204 - *Network Path Outage / Extended Loss / DNS Errors*:205206 ```text207 resource.type = "networkmanagement.googleapis.com/NetworkPath" AND logName =~ "insights_alarm" AND (jsonPayload.alarm_severity = "MAJOR" OR jsonPayload.alarm_severity = "CRITICAL") AND jsonPayload.state = "RAISED" AND jsonPayload.alarm_type =~ "QUALITY_OF_SERVICE" AND jsonPayload.rule =~ "Outage" AND NOT jsonPayload.noise_conditions:*208 ```209210 *(Substitute `jsonPayload.rule =~ "Extended loss"` or `"Multiple DNS211 errors"` with `alarm_severity = "MINOR"` as needed.)*212 - *Web Path Multiple Web Errors*:213214 ```text215 resource.type = "networkmanagement.googleapis.com/WebPath" AND logName =~ "insights_alarm" AND jsonPayload.alarm_severity = "MAJOR" AND jsonPayload.state = "RAISED" AND jsonPayload.alarm_type =~ "QUALITY_OF_SERVICE" AND jsonPayload.rule =~ "Multiple Web errors" AND NOT jsonPayload.noise_conditions:*216 ```217 - *Monitoring Point Offline and Network Path MTU Change Events*:218219 ```text220 resource.type = "networkmanagement.googleapis.com/MonitoringPoint" AND logName =~ "insights_event" AND jsonPayload.event_type = "MONITORING_POINT_OFFLINE"221 ```222223 ```text224 resource.type = "networkmanagement.googleapis.com/NetworkPath" AND logName =~ "insights_event" AND jsonPayload.event_type = "MTU_CHANGE"225 ```226- **Cloud Logging (`gcloud logging read`)**: Query path alarms (`logName =~227 "insights_alarm"`) and operational lifecycle events (`logName =~228 "insights_event"`) exported to Cloud Logging (see229 [Set up logging](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights/set-up-logging)230 for `jsonPayload` field schemas and event types). Because alarm state231 transitions (`RAISED`, `UPDATED`, `CLEARED`) are logged as separate entries232 sharing the same `jsonPayload.alarm_id`, determine currently active alarms233 by checking that the latest entry for an `alarm_id` has not transitioned to234 `CLEARED`.235- **Cloud Monitoring (REST API `projects.timeSeries.list`)**: Query path236 performance metrics (`NetworkPath` and `WebPath`, filtered by237 `resource.labels.path_id`) via `GET238 "https://monitoring.googleapis.com/v3/projects/PROJECT_ID/timeSeries"` with239 `Authorization: Bearer $(gcloud auth application-default240 print-access-token)` in Cloud Monitoring (see241 [Monitoring metrics](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights/monitoring-metrics)242 and243 [View dashboards](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights/view-dashboards)).244245### 7. Deployment Diagnostics and Troubleshooting246247To diagnose a Monitoring Point deployment across any platform:2482491. **Google Cloud Registration**: Check that `connectionStatus` is `ONLINE` in250 `monitoring-points list` (or `describe`) to verify the Monitoring Point is251 registered and connected to Cloud Network Insights.2522. **Model-Specific Workload, Host, and Appliance Health**: Inspect the253 Monitoring Point runtime, container/Kubernetes workload, or v35 Web Admin254 status on the target platform using the model-specific troubleshooting255 guides in256 [Monitoring Point Deployment Reference](references/monitoring-point-deployment.md),257 [Broadcom Troubleshooting Monitoring Points](https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/appneta-for-google-cloud-network-insights/GA/troubleshooting-section/troubleshooting.html),258 and259 [Troubleshooting Cloud Network Insights](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights/troubleshooting).2603. **Network, Proxy, and Firewall Rules**: Verify the target environment's261 firewall, Web Proxy, custom CA certificate, and gRPC/SSL inspection bypass262 settings (`data.na1.cni.appneta.com`, `content.na1.cni.appneta.com`,263 `comms.na1.cni.appneta.com`, or `.p.` endpoints for Private Service Connect)264 against265 [Broadcom Firewall Configuration](https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/appneta-for-google-cloud-network-insights/GA/appliance-firewall.html)266 and267 [Add Monitoring Points](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights/add-monitoring-points).268269## Reference Documentation270271For detailed guides, complete payloads, and templates:272273- [Monitoring Point Deployment Reference](references/monitoring-point-deployment.md):274 Deployment guides and command references across all 7 platforms (container,275 Helm, GCE VM Terraform, AWS, Azure, VMware, KVM).276- [Monitoring Policy Configuration Reference](references/monitoring-policies.md):277 Network and Web monitoring policy JSON payloads and AppNeta API workflows.278- [Google Cloud Network Insights Documentation](https://cloud.google.com/network-intelligence-center/docs/cloud-network-insights):279 Official Google Cloud documentation for Cloud Network Insights setup,280 concepts, and operations.281- [Broadcom AppNeta for Cloud Network Insights Documentation](https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/appneta-for-google-cloud-network-insights/GA.html):282 Broadcom AppNeta monitoring points, path performance, and API guides.