davila7/claude-code-templates / cli-tool/components/skills/development/google-cloud-networking-observability
google-cloud-networking-observability
VerifiedInvestigates Google Cloud networking issues by analyzing logs, metrics, and diagnostics. Use when investigating VPC Flow Logs, NAT, firewall, or threat logs, querying latency and throughput metrics, or running Connectivity Tests for path diagnostics.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.0 KB |
| references/cloud-nat-analysis.md | markdown | 2.7 KB |
| references/connectivity-tests.md | markdown | 1.4 KB |
| references/firewall-analysis.md | markdown | 3.0 KB |
| references/mcp-usage.md | markdown | 2.6 KB |
| references/metrics-analysis.md | markdown | 3.0 KB |
| references/threat-analysis.md | markdown | 5.7 KB |
| references/vpc-flow-analysis.md | markdown | 4.8 KB |
references/metrics-analysis.md
View on GitHub# Networking Metrics Reference
## Common Troubleshooting Metrics
- **RTT (Latency)**:
`networking.googleapis.com/cloud_netslo/active_probing/rtt`
- **Packet Loss**:
`networking.googleapis.com/cloud_netslo/active_probing/probe_count`
- **VM Throughput**:
`compute.googleapis.com/instance/network/received_bytes_count`
- **VM Sent Packets**:
`compute.googleapis.com/instance/network/sent_packets_count`
- **VM Received Packets**:
`compute.googleapis.com/instance/network/received_packets_count`
- **NAT Port Exhaustion**:
`compute.googleapis.com/nat/dropped_sent_packets_count`
- **NAT Sent Packets**: `compute.googleapis.com/nat/sent_packets_count`
- **VPN Dropped Received Packets**:
`vpn.googleapis.com/network/dropped_received_packets_count`
- **VPN Dropped Sent Packets**:
`vpn.googleapis.com/network/dropped_sent_packets_count`
- **Internal Latency (RTT)**: `networking.googleapis.com/vm_flow/rtt`.
Measures internal VM-to-VM traffic within Google Cloud.
- **External Latency (RTT)**:
`networking.googleapis.com/vm_flow/external_rtt`. Measures traffic to and
from the internet.
## Distribution Parsing Standard
When querying metrics of type DISTRIBUTION (like RTT), align the data with
`ALIGN_PERCENTILE_50` to ensure the output can be parsed as a simple numeric
value.
## Dynamic Discovery
- **Primary ([Cloud Monitoring MCP](mcp-usage.md#cloud-monitoring-mcp))**: Use
`list_metric_descriptors` with a filter.
- **Prefix**: Filter by prefix, using `starts_with()`. Common prefixes:
- `metric.type = starts_with("networking.googleapis.com/")`
- `metric.type = starts_with("router.googleapis.com/")`
- `metric.type = starts_with("vpn.googleapis.com/")`
- `metric.type = starts_with("compute.googleapis.com/")`
- **Substring**: `metric.type = has_substring("network") OR metric.type =
has_substring("packet") OR metric.type = has_substring("nat")`
- **Fallback (CLI/CURL)**: If MCP tools not available, use `gcloud` or `curl`.
```bash
curl -s -H "Authorization: Bearer $(gcloud auth print-access-token)"
"https://monitoring.googleapis.com/v3/projects/{project_id}/metricDescriptors?filter=metric.type=starts_with(%22{prefix}%22)"
| jq -r '.metricDescriptors[] | "\(.type): \(.description)"'
curl -s -H "Authorization: Bearer $(gcloud auth print-access-token)" \
"https://monitoring.googleapis.com/v3/projects/{project_id}/timeSeries?" \
"filter=metric.type%3D%22{metric_name}%22&" \
"interval.startTime={start_time}&" \
"interval.endTime={end_time}&" \
"aggregation.alignmentPeriod=3600s&" \
"aggregation.perSeriesAligner=ALIGN_PERCENTILE_50" \
| jq '.timeSeries[] | {metric: .metric.type, points: .points[:5]}'
```
- **Detailed Schema**: ALWAYS query the full descriptor for a specific metric
before use to identify available labels. Metric types like `vm_flow/rtt`
often use `resource.labels.zone` for the local zone and
`metric.labels.remote_zone` for the peer.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |