[[["易于理解","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,["# Troubleshoot Network Topology\n=============================\n\nUse the following guidance to troubleshoot common issues with Network Topology.\nTo learn more about Network Topology, see the\n[overview](/network-intelligence-center/docs/network-topology/concepts/overview).\n\nNo nodes were found for this graph\n----------------------------------\n\nCheck that your resources aren't hidden by a filter. For more information, see\n[Filtering specific entities](/network-intelligence-center/docs/network-topology/how-to/using-network-topology#filter-entities).\n\nOnly resources that are created by the current project are visible to that\nproject. If you are using Shared VPC, you might have your network in the\nhost project and resources in service projects. In the host project,\nNetwork Topology doesn't visualize the Shared VPC network or\nits resources because the resources are in service projects. For information\nabout how to visualize resources in the Shared VPC network, see [Adding\nmultiple projects to a single graph](/network-intelligence-center/docs/network-topology/how-to/using-network-topology#multi-project).\n\n### Why don't I see traffic between entities?\n\nFor information about why you might not see traffic between entities, see\nthe following:\n\n- At least one supported resource on either end of a connection must communicate with the other for traffic between them to become visible.\n- Network Topology might not display connections for resources that have a very low amount of traffic between them.\n\nFor more information, see the [Communication](#communication) section\nand [Resources and traffic](/network-intelligence-center/docs/network-topology/concepts/overview#supported_resources)\nin the overview.\n\nAn instance or load balancer is missing\n---------------------------------------\n\nYou might have an existing instance or load balancer that isn't shown in a\nNetwork Topology graph. The following sections describe scenarios\nwhen a resource isn't shown.\n\n### Projects and metrics scope\n\nThe Network Topology graph shows communication between resources in\nyour existing project or Monitoring's\n[metrics scope](/monitoring/settings). If a missing\nresource is in a different project than the currently selected project, check\nthat both projects are visible to the selected project's metrics scope.\nFor more information, see [Adding multiple projects to a single\ngraph](/network-intelligence-center/docs/network-topology/how-to/using-network-topology#multi-project).\n\n### Communication\n\nThe Network Topology graph shows only the resources that are\ncommunicating with at least one other entity in the selected hourly segment.\nIf an instance or load balancer didn't send or receive traffic during the\nselected hour, Network Topology doesn't visualize it. Check that\nyou've selected a segment when the instance or load balancer is in\ncommunication with another entity. For more information, see [Data collection\nand freshness](/network-intelligence-center/docs/network-topology/concepts/overview#data).\n\n### Filters and entity selection\n\nIn a Network Topology graph, you can add filters to view the\nspecified resources and the resources that they communicate with. All other resources\nare hidden. Check that your filters include the instances or load balancers that\nyou want to view.\n\nNetwork Topology also includes a pane where you can choose to hide or\nshow particular entities. Check that you are showing (have selected) the\nresource types that you want to view. For example, if you clear the\n**Instances** checkbox, all instances are hidden.\n\nFor more information, see\n[Filtering specific entities](/network-intelligence-center/docs/network-topology/how-to/using-network-topology#filter-entities).\n\nWhen I expand some entities, Network Topology skips some levels of the hierarchy\n--------------------------------------------------------------------------------\n\nIn cases when there's only a single entity at any particular level,\nNetwork Topology skips that level or levels until it reaches a level\nwhere multiple entities can be aggregated or until it reaches the base entity.\n\nNetwork Topology always shows some levels of a hierarchy, such as the\nregion for a virtual machine (VM) instance. For example, if you have a single VM\nin a region, Network Topology shows that region, but when you expand\nthe region, Network Topology skips directly to the VM instance\nwithout showing its zone.\n\nYou can still view the full hierarchy for an entity by clicking it and viewing\nits [details pane](/network-intelligence-center/docs/network-topology/concepts/graph-overview).\n\nSome lines don't show metric values\n-----------------------------------\n\nFor information about why some lines don't show metric values, see the following:\n\n- In some cases, Network Topology has metric values but doesn't\n have enough room to show them. Network Topology shows a bulge in the\n line to indicate that metric values are available. Drag the connecting\n objects further apart to show the metric value.\n\n- Metrics might not be available between entities at all levels of their\n aggregation hierarchies. For example, metrics are available from VMs to\n regions, but not from VMs to other VMs.\n\n- Not all metrics apply to all connections. For information about the supported\n metrics for each connection, see the\n [Metrics reference](/network-intelligence-center/docs/network-topology/reference/metrics-reference).\n\n- For packet loss and latency, metric values show `Not available` if the\n sample rate for the metric is too low to be reliable or if the\n Cloud Monitoring API does not return a value. For more information about how\n these metrics are calculated, see the\n [Metrics](/network-intelligence-center/docs/performance-dashboard/concepts/overview#metrics)\n section of the Performance Dashboard overview.\n\n- Latency appears only on lines that represent a single connection. It is not\n aggregated on lines that branch into multiple connections.\n\nDisplayed throughput is higher than expected\n--------------------------------------------\n\nTo view details about a throughput value, click the metric to see a time\nseries chart. You can see how throughput evolved over time.\n\nIf you have [VPC Flow Logs](/vpc/docs/using-flow-logs) enabled and export\nthose logs to BigQuery, you can use an automatically generated query to\nsee the flows related to the throughput values. For more information, see [Using\ngenerated queries](/network-intelligence-center/docs/network-topology/how-to/using-network-topology#queries).\n\nThe graph contains too many nodes and connections\n-------------------------------------------------\n\nUse filtering or the entity selection pane to reduce the clutter. For more\ninformation, see\n[Filtering specific entities](/network-intelligence-center/docs/network-topology/how-to/using-network-topology#filter-entities).\n\nThe full graph is too big to be handled\n---------------------------------------\n\nIf the topology graph is too large to be displayed in a browser, a truncated\ngraph is displayed. Some connections and nodes might be missing from the\ndisplayed graph.\n| **Note:** Metrics are still accurate; the truncation only affects the existence of some connections and possibly some nodes.\n\n- Remove some projects or resources from this metrics scope.\n- To reduce the graph's size, show data only for the current project.\n\nIn a Google Cloud zone, there are two GKE clusters with the same name\n---------------------------------------------------------------------\n\nGKE cluster names are unique for each GKE\nlocation, such as a Google Cloud region or a Google Cloud zone. You\ncan set up a GKE cluster in a Google Cloud\nzone and a second GKE cluster with the same name in the\nencompassing Google Cloud region. In the **Network Topology\nGKE** view, these clusters are shown as two clusters with the\nsame name in the same zone. You can see the cluster location below the name\nof the cluster and in the right panel after you click the node.\n\nWhat's next\n-----------\n\n- [Get support](/network-intelligence-center/docs/network-topology/support/getting-support)"]]
