CodeWithClarity

  GCP Network Monitoring & Network Intelligence 1. Why Network Monitoring? In a large Google Cloud environment, you may have: Multiple VPC networks Multiple network interconnections Many teams managing different parts of the network This creates challenges such as: Lack of network visibility Performance issues Network bottlenecks Connectivity problems Difficulty analyzing network behavior The goal of network monitoring is to get visibility + detect problems + troubleshoot + prevent outages . 2. Cloud Monitoring Cloud Monitoring helps you monitor the performance and utilization of your Google Cloud resources. You can create custom dashboards containing charts for the metrics you care about. Example metrics For VM instances, you can monitor: CPU utilization Packets sent Packets received Bytes sent Bytes received Packets dropped by firewall So, simply: Cloud Monitoring = See what is happening in your infrastructure. Dashboard customization Charts can be customized using: Filters...

  GCP Networking — Shared VPC vs VPC Peering 1. First, correct the mental model There are two different goals: Shared VPC You want multiple projects to use one centrally managed VPC . Host Project | Shared VPC / | \ / | \ Project A Project B Project C VM VM VM Think: One network → multiple projects VPC Network Peering You already have separate VPC networks and want them to communicate privately. VPC-A ←──── Private Peering ────→ VPC-B Think: Separate networks → private connection 2. Same organization vs different organizations Different organizations If you have: Organization A | VPC-A and: Organization B | VPC-B and you want private communication: VPC-A ←──── Peering ────→ VPC-B You use VPC Network Peering . Shared VPC is designed around projects within the same organization . 3. Same project The lesson says: ...