cloud-network-insights

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

对于使用此

skill

执行命令时涉及的所有

gcloud

CLI、REST API 和 MCP 归因要求，请遵循使用归因中的说明。

🛑 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.

确定请求的任务：判断用户是否正在尝试服务启用、检查激活状态、下载/安装或排查 Monitoring Points (MPs)、配置 AppNeta 监控策略或告警规则、验证已预配的资源和路径、配置告警策略，或查询 Cloud Logging 告警和 Cloud Monitoring 指标。
执行并呈现结果：执行完成任务所需的最小命令集或 API 调用，或提供准确指导。
明确结论：对于状态和验证查询，立即报告明确状态（例如
```
ACTIVE
```
、
```
ACTIVATING
```
或路径列表）。

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.

Cloud Network Insights 与 Broadcom AppNeta 合作，为跨云网络可观测性提供全面的合成监控。它使用安装在 Google Cloud、本地数据中心、其他公共云（如 AWS 或 Azure）以及公共互联网中的 Monitoring Points (MPs) 监控网络和 Web 路径。

此 skill 自动执行接入、服务启用、Monitoring Point 部署、策略创建和路径验证。

Procedures and CUJs

流程与 CUJs

1. Service Enablement and Status

1. 服务启用与状态

Enable API:

bash

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

bash

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:

bash

gcloud network-management network-monitoring-providers \
  describe PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID \
  --format=json

Check that

.state

ACTIVE

. (

ACTIVATING

indicates the backend is provisioning AppNeta resources.)

Delete Provider (Cleanup):

bash

gcloud network-management network-monitoring-providers delete PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID

启用 API：

bash

gcloud services enable networkmanagement.googleapis.com --project=PROJECT_ID

创建 Provider（使用

external

以匹配 Google Cloud 控制台默认值，或使用自定义

PROVIDER_ID

）：

bash

gcloud network-management network-monitoring-providers create PROVIDER_ID \
  --provider-type=EXTERNAL \
  --location=global \
  --project=PROJECT_ID

⚠️ 如果此命令因未接受服务条款而失败，请将用户引导至 Google Cloud 控制台接入页面：
https://console.cloud.google.com/net-intelligence/cloud-network-insights/onboarding?project=PROJECT_ID

验证状态：

bash

gcloud network-management network-monitoring-providers \
  describe PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID \
  --format=json

检查

.state

是否为

ACTIVE

。（

ACTIVATING

表示后端正在预配 AppNeta 资源。）

删除 Provider（清理）：

bash

gcloud network-management network-monitoring-providers delete PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID

2. Monitoring Point Deployment and Verification

2. Monitoring Point 部署与验证

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.

Cloud Network Insights 支持 7 种不同的 Monitoring Point 部署类型：

container

、

helm

、

gce-vm

、

aws-ec2

、

azure-vm

、

vmware

和

kvm

。

平台选择：切勿假定默认部署类型。开始操作前，应确定目标环境，或提示用户提供目标环境。
流程与命令：有关所有必需参数、下载命令、部署清单和状态验证命令（
```
monitoring-points list
```
），请参阅 Monitoring Point 部署参考。

3. Monitoring Policy and Alarm Rule Configuration (AppNeta)

3. 监控策略与告警规则配置（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.

监控策略用于配置由 Monitoring Points 执行的主动合成网络和 Web 测试，告警规则则定义用于触发路径告警的阈值和评估窗口。

策略类型（
/api/v4/monitoringPolicy
）：
- 网络监控策略：通过 TCP 或 UDP 监控目标 IP 的数据包丢失、延迟和抖动，或在两个 Monitoring Points 之间执行双端测试。
- Web 监控策略：执行 HTTP/HTTPS 应用合成检查（例如带状态码 200 断言的 GET 请求）。
创建前检查：始终先查询
```
GET /api/v4/monitoringPolicy
```
，确认目标名称的策略是否已存在，然后再创建新策略，以避免重复创建资源和 API 冲突。
告警规则（仅限 AppNeta Web UI）：告警规则在 AppNeta Web UI 中配置（位于 Alarms > Alarm Rules；请参阅 Broadcom 告警规则）， REST API v4 不支持此操作。
流程与载荷：有关身份验证令牌生成、组织发现和 REST JSON 载荷，请参阅监控策略配置参考。

4. Verifying Provisioned Paths in Google Cloud

4. 验证 Google Cloud 中已预配的路径

Once policies are configured and MPs are online, verify provisioned paths:

List Network Paths:

bash

gcloud network-management network-monitoring-providers network-paths list \
  --network-monitoring-provider=PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID \
  --format=json

List Web Paths:

bash

gcloud network-management network-monitoring-providers web-paths list \
  --network-monitoring-provider=PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID \
  --format=json

配置策略并确认 MPs 上线后，验证已预配的路径：

列出网络路径：

bash

gcloud network-management network-monitoring-providers network-paths list \
  --network-monitoring-provider=PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID \
  --format=json

列出 Web 路径：

bash

gcloud network-management network-monitoring-providers web-paths list \
  --network-monitoring-provider=PROVIDER_ID \
  --location=global \
  --project=PROJECT_ID \
  --format=json

5. Querying Cloud Network Insights Resources and State

5. 查询 Cloud Network Insights 资源和状态

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]

发现 Provider 名称：运行
```
gcloud network-management    network-monitoring-providers list --location=global --project=PROJECT_ID
```
以获取 Provider ID（
```
PROVIDER_ID
```
）。通过 Google Cloud 控制台启用时， Provider ID 为
```
external
```
；如果手动创建，则为自定义名称。

查询子资源：向子资源命令（如

list

和

describe

）传入

--network-monitoring-provider=PROVIDER_ID

和

--location=global

：

Monitoring Points：

gcloud network-management network-monitoring-providers monitoring-points [list|describe]

网络路径：

gcloud network-management network-monitoring-providers network-paths [list|describe]

Web 路径：

gcloud network-management network-monitoring-providers web-paths [list|describe]

6. Alert Policies, Cloud Logging, and Cloud Monitoring Metrics

6. 告警策略、Cloud Logging 和 Cloud Monitoring 指标

Alert Policies (
gcloud monitoring policies
): Create log-matched alert policies (

conditionMatchedLog.filter

, including

alertStrategy.notificationRateLimit

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:

bash

# 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:

text

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:

text

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:

text

resource.type = "networkmanagement.googleapis.com/MonitoringPoint" AND logName =~ "insights_event" AND jsonPayload.event_type = "MONITORING_POINT_OFFLINE"

text

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).

告警策略（
gcloud monitoring policies
）：为路径告警和运行事件创建基于日志匹配的告警策略（

conditionMatchedLog.filter

，包括

POLICY_FILE

中的

alertStrategy.notificationRateLimit

）（请参阅设置告警和通知）。对于

insights_alarm

策略，默认包含

AND NOT jsonPayload.noise_conditions:*

，以过滤频繁或突发噪声；除非用户要求包含噪声告警。

bash

# 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

Google Cloud 控制台告警模板的

conditionMatchedLog.filter

示例：

网络路径中断 / 持续丢包 / DNS 错误：

text

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:*

（根据需要，使用
alarm_severity = "MINOR"
替换
jsonPayload.rule =~ "Extended loss"
或
"Multiple DNS errors"
。）

Web 路径多项 Web 错误：

text

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 离线及网络路径 MTU 变更事件：

text

resource.type = "networkmanagement.googleapis.com/MonitoringPoint" AND logName =~ "insights_event" AND jsonPayload.event_type = "MONITORING_POINT_OFFLINE"

text

resource.type = "networkmanagement.googleapis.com/NetworkPath" AND logName =~ "insights_event" AND jsonPayload.event_type = "MTU_CHANGE"

Cloud Logging（
gcloud logging read
）：查询导出到 Cloud Logging 的路径告警（
```
logName =~ "insights_alarm"
```
）和运行生命周期事件（
```
logName =~ "insights_event"
```
）（有关
```
jsonPayload
```
字段架构和事件类型，请参阅设置日志记录）。由于告警状态转换（
```
RAISED
```
、
```
UPDATED
```
、
```
CLEARED
```
）会作为共享同一
```
jsonPayload.alarm_id
```
的独立条目记录，因此应检查某个
```
alarm_id
```
的最新条目是否尚未转换为
```
CLEARED
```
，以确定当前活动的告警。

Cloud Monitoring（REST API
projects.timeSeries.list
）：通过

GET "https://monitoring.googleapis.com/v3/projects/PROJECT_ID/timeSeries"

查询 Cloud Monitoring 中的路径性能指标（

NetworkPath

和

WebPath

，按

resource.labels.path_id

过滤），请求使用

Authorization: Bearer $(gcloud auth application-default print-access-token)

（请参阅监控指标和查看仪表板）。

7. Deployment Diagnostics and Troubleshooting

7. 部署诊断与故障排查

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.

要诊断任意平台上的 Monitoring Point 部署：

Google Cloud 注册：在
```
monitoring-points list
```
（或
```
describe
```
）中检查
```
connectionStatus
```
是否为
```
ONLINE
```
，以验证 Monitoring Point 已注册并连接到 Cloud Network Insights。
特定于型号的工作负载、主机和设备运行状况：使用 Monitoring Point 部署参考、 Broadcom Troubleshooting Monitoring Points和 Troubleshooting Cloud Network Insights 中的型号特定排查指南，检查目标平台上的 Monitoring Point 运行时、容器/Kubernetes 工作负载或 v35 Web Admin 状态。
网络、代理和防火墙规则：对照 Broadcom 防火墙配置和添加 Monitoring Points，验证目标环境中的防火墙、Web Proxy、自定义 CA 证书以及 gRPC/SSL 检查绕过设置（
```
data.na1.cni.appneta.com
```
、
```
content.na1.cni.appneta.com
```
、
```
comms.na1.cni.appneta.com
```
，或用于 Private Service Connect 的
```
.p.
```
端点）。

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.

有关详细指南、完整载荷和模板：

Monitoring Point 部署参考：涵盖全部 7 种平台的部署指南和命令参考（container、Helm、GCE VM Terraform、AWS、Azure、VMware、KVM）。
监控策略配置参考：网络和 Web 监控策略 JSON 载荷及 AppNeta API 工作流。
Google Cloud Network Insights 文档：Google Cloud 关于 Cloud Network Insights 设置、概念和操作的官方文档。
Broadcom AppNeta for Cloud Network Insights 文档：Broadcom AppNeta Monitoring Points、路径性能和 API 指南。