[[["易于理解","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 Analyzer overview\n\nNetwork Analyzer automatically monitors your Virtual Private Cloud (VPC)\nnetwork configurations and detects misconfigurations and suboptimal\nconfigurations. It provides insights about\nnetwork topology, firewall rules, routes, configuration dependencies, and\nconnectivity to services and applications. It identifies network failures,\nprovides root cause information, and suggests possible resolutions.\n\nNetwork Analyzer runs continuously and triggers relevant analyses based on\nnear real-time configuration updates in your network. If a network failure is\ndetected, it tries to correlate the failure with recent configuration changes to\nidentify root causes. Wherever possible, it provides recommendations to suggest\ndetails about how to fix the issues.\n\nNetwork insight groups and types\n--------------------------------\n\nThe results from Network Analyzer analyses are known as *insights*.\nInsights are grouped into the following categories:\n\n- VPC network\n- Network services\n- Kubernetes engine\n- Hybrid connectivity\n- Managed services\n\nFor more information about these groups and their related insight types, see\n[Insight groups and types](/network-intelligence-center/docs/network-analyzer/insight-groups-types).\n\nAnalysis schedule\n-----------------\n\nNetwork Analyzer generates insights whenever relevant configuration changes\nare made, as well as periodically. Analyses are triggered approximately\nten minutes after a related configuration change is made. Periodic analyses are\nperformed at least once daily.\n\nAnalyses are batched to handle frequent configuration updates.\n\nInsight attributes\n------------------\n\nEach insight has key attributes that help you to understand and take corrective\nactions.\n\n### Priority\n\nSpecifies the criticality of the insight depending on the severity of the issue.\n\n- **Critical:** Include service-impacting issues with large scope impact (such as all the VMs, global, or multi-regions).\n- **High:** Include service impacting issues, but may not be of a large scope.\n- **Medium:** Include issues that have service impact or prevent proper service usage.\n- **Low:** Include warnings of predictive failure in the future (such as utilization) or for optimization (such as recommendations to reduce cost and improve redundancy).\n\n### Resource name\n\nProvides information about the resource where the issue is found.\n\n### Resource type\n\nThe type of the resource according to Google Cloud API\n[resource definitions](/resource-manager/reference/rest).\n\n### Project\n\nThe ID of the project to which the resource belongs.\n\n### Insight type\n\n- **Info:** Provides information about the resources.\n- **Warning:** Indicates a warning condition, which could be service degradation or lack of redundancy.\n- **Error:** Indicates an error condition where service usability or performance is already impacted.\n\n### Network insight\n\nProvides a single-line description of the issue type being reported.\n\n### First report time\n\nSpecifies the time when an issue is detected for the first time. If the issue\npersists, any later analysis (triggered by the system automatically) reports the\nsame issue again with this latest analysis time as the last run time.\n\n### Status\n\nIndicates whether the insight is active, fixed (no longer being reported), or\na user has dismissed the insight.\n\n- **Active:** The insight exists at the time of the query.\n- **Fixed:** The insight was reported before but was resolved at the time of the query.\n- **Dismissed:** The insight has been dismissed by a user.\n\n### Insight details\n\nProvides more detailed information of the finding, and includes related\nconfiguration changes where applicable.\n\nShared VPC insights\n-------------------\n\nFor Shared VPC cases, there are two scenarios:\n\n- **Host project:** Network Analyzer provides relevant information for VPC networks in the host project, such as IP address utilization insights that display the IP address allocation percentage of subnets. For such insights, the information from service projects is automatically aggregated to derive the insight information. In the IP address utilization insights, the VMs and load balancers in the service projects are included in the calculation of IP address allocation.\n- **Service project:** Services and applications running in service projects have their analyses done in service projects. Example insights include: load balancer insights, GKE insights, and Cloud SQL insights. If these services use the host project VPC network, the analysis automatically includes the host VPC network information such as firewall rules and routes.\n\nMultiple projects\n-----------------\n\nTo view multiple projects in Network Analyzer, configure a\nmetrics scope and add monitored projects to it.\n\nWhen you add projects to a metrics scope, then this metrics scope lets you\nmonitor the data for the scoping project and the monitored projects. From this\nmetrics scope, you can access the combined metrics of the scoping project\nand the monitored projects. For more information, see\n[Viewing metrics for multiple projects](/monitoring/settings/multiple-projects).\n\nTo make use of an existing metrics scope and monitor multiple Google Cloud\nprojects in a single view, select the scoping project using the Google Cloud console\nproject picker or the **Change Scope** button. You can also select a single\nmonitoring project using these options.\n\nOpt out\n-------\n\nIf you do not want to have projects in your organization analyzed by\nNetwork Analyzer, you can go to the Transparency and Control Center\nto opt out of the Network Analyzer data processing group.\nTo change opt-out settings, you must have the Data Processing Controls\nResource Admin role (`roles/dataprocessing.admin`). For more\ninformation about opting out, see\n[Opting out of data processing](/recommender/docs/opting-out)."]]
