[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-25。"],[],[],null,["# Network Topology metrics\n========================\n\nThis document describes Cloud Monitoring metrics and metadata, which\nyou can view in a Network Topology visualization for each entity and\nconnection.\n\n- **Metadata** describes data such as name, description, and location.\n- **Metrics** describe data such as traffic, latency, and packet loss, which are the supported metrics for connections.\n\nFor each Network Topology hierarchy, the Google Cloud console displays a\nsingle metric for Compute Engine virtual machine (VM) instance entities and\nregion entities, as well as for connections. You can change this default metric.\n\nFor more information, see the\n[Network Topology overview](/network-intelligence-center/docs/network-topology/concepts/overview)\nand [Graph interface elements](/network-intelligence-center/docs/network-topology/concepts/graph-overview).\n\nFor steps describing how to work with metrics and metadata, see\n[Audit your networking configuration with Network Topology](/network-intelligence-center/docs/network-topology/how-to/using-network-topology).\n\nMetrics for VM or regional entities\n-----------------------------------\n\nThis section lists metrics for VMs or regional entities.\n\nMetrics for connections between entities\n----------------------------------------\n\nThis section lists metrics for connections between entities.\n\nSome connections support packet loss or latency metrics. Packet loss is based on\nprobers that estimate the packet loss that you might experience, while latency and\nother metrics are based on your own traffic.\n\nIf there are not enough probes or traffic to calculate a high confidence value\nfor packet loss or latency, Network Topology displays an asterisk\n(\\*) next to the value on the graph. For more information about how these\nmetrics are calculated, see the\n[Metrics](/network-intelligence-center/docs/performance-dashboard/concepts/overview#metrics) section of the Performance Dashboard overview.\n\n### Connections in the VM hierarchy\n\nThis section lists metrics for connections in the aggregation hierarchy where VM\nis the base entity. For more information about entities and their aggregation\nhierarchies, see\n[Resources and traffic](/network-intelligence-center/docs/network-topology/concepts/overview#supported_resources).\n\n^1^ VM-to-VM flows are not available at all aggregation\nlevels. For example, the VM-to-VM flow is not available, but the\nVM-to-region flow is available.\n\n^2^ Packet loss is available only for regions and zones.\n\n### Connections in the GKE hierarchy\n\nThis section lists metrics for connections in the aggregation hierarchy where\nthe GKE node is the base entity. For more information about entities and their\naggregation hierarchies, see\n[Resources and traffic](https://cloud.google.com/network-intelligence-center/docs/network-topology/concepts/overview#supported_resources).\n\n^1^ Pod-to-Pod flows are not available at all aggregation levels. For example,\nthe Pod-to-Pod flow is not available, but the Pod-to-region flow is available.\n\n### Client to load balancing\n\nThis section lists metrics and metadata for traffic from external or internal\nclients to different types of Cloud Load Balancing.\n\n^3^For external clients, Network Topology supports only\naggregation levels from `Country` and higher.\n\n### Load balancing to backend instance groups\n\nThis section lists metrics and metadata from different types of\nCloud Load Balancing to instance group backends.\n\n### Load balancing to GKE node pools and nodes\n\nThis section lists metrics and metadata from different types of\nCloud Load Balancing to GKE node pools and nodes.\n\n### VLAN attachments\n\nThis section lists metrics and metadata for the data transferred between your\nVPC network and the on-premises network, as counted by the VLAN\nattachment. An on-premises network can refer to any remote network that is outside\nthe Google Cloud domain. The connection between Google Cloud and\non-premises can traverse either dedicated or partner Interconnect devices.\n\n### VPN tunnels\n\nThis section lists metrics and metadata for the data transferred between your\nVPC network and the on-premises network, as counted by the VPN tunnel.\n\n### VM to VLAN attachments\n\nThis section lists metrics and metadata for the data transferred between your\nVM and VLAN attachment. The connection between Google Cloud and\non-premises can traverse either dedicated or partner Interconnect devices.\n\n### VM to VPN tunnels\n\nThis section lists metrics and metadata for the data transferred between your\nVM and VPN tunnels.\n\n### Client to Google services\n\nThis section lists metrics and metadata for traffic from internal clients to\ndifferent types of [Google-managed services](/network-intelligence-center/docs/network-topology/concepts/overview#google-services).\n\n### Router appliance\n\nThis section lists metrics and metadata for the data transferred between your\nVPC network and the on-premises network, as counted by the\nrouter appliance instance.\n\n### VM to router appliance instance\n\nThis section lists metrics and metadata for the data transferred between your\nVM and router appliance instances."]]
