google-cloud-recipe-networking-observability

Correlate Google Cloud logs, metrics, and diagnostics to identify networking misconfigurations and bottlenecks.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill google-cloud-recipe-networking-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-cloud-recipe-networking-observability
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/networking-observability
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill google-cloud-recipe-networking-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineers and operators diagnose Google Cloud networking issues by correlating logs, metrics, and diagnostics across VPC Flow Logs, NAT, firewall, and threat logs to identify root causes quickly.

Core Features & Use Cases

  • Analyze logs and metrics from Google Cloud to pinpoint connectivity issues and performance bottlenecks.
  • Use for path diagnostics with Connectivity Tests to validate reachability and routing between endpoints.
  • Reference best-practice workflows for NAT, firewall rules, and threat logs to resolve incidents faster.
  • Example: quickly triage a NAT port exhaustion scenario by correlating NAT logs with flow metrics and firewall hits.

Quick Start

Select the relevant log source (VPC Flow Logs, NAT, firewall, or threat logs) and pull the top latency and drop indicators from the associated metrics to start the diagnosis.

Frequently Asked Questions about google-cloud-recipe-networking-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Google Cloud networking issues using VPC Flow Logs?

Diagnose Google Cloud networking issues by correlating VPC Flow Logs with metrics and Connectivity Tests to identify misconfigurations and performance bottlenecks. Select the relevant log source and pull top latency and drop indicators to start the diagnosis.

What is the best way to troubleshoot Cloud NAT port exhaustion?

Troubleshoot Cloud NAT port exhaustion by correlating NAT logs with flow metrics and firewall hits to identify the root cause. This approach pinpoints connectivity issues and performance bottlenecks across projects and networks quickly.

Can I use Connectivity Tests to validate routing between Google Cloud endpoints?

Connectivity Tests validate reachability and routing between endpoints across projects and networks. Use these path diagnostics alongside Cloud Logging and Cloud Monitoring to triage complex networking troubleshooting scenarios.

Do I need BigQuery to analyze Google Cloud firewall and threat logs?

BigQuery is optional for analyzing firewall and threat logs. You need access to Cloud Logging and Cloud Monitoring to query logs and metrics, while BigQuery MCP or MCP-enabled tooling can be used optionally for deeper analysis.

Why does my Google Cloud network connectivity fail across projects?

Cross-project network connectivity fails due to misconfigurations identified by correlating firewall logs, VPC Flow Logs, and path diagnostics. Analyze drop indicators and latency metrics from Cloud Monitoring to isolate the bottleneck.