[[["易于理解","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-29。"],[],[],null,["# Performance Dashboard metrics reference\n\nPerformance Dashboard exports packet loss and latency metrics to\nCloud Monitoring. You can create your own dashboard in\nMonitoring, and you can create dashboard charts and alerts that\nuse Performance Dashboard metrics.\n\nPacket loss metrics\n-------------------\n\nPerformance Dashboard only exposes certain fields in its packet loss\ncharts. Monitoring exposes all collected metric fields for the\nresource:\n\n- Resource type: `gce_zone_network_health`\n- Metric: `networking.googleapis.com/cloud_netslo/active_probing/probe_count`\n- Description: Number of probes\n\nPacket loss is calculated as a ratio of failed probes over total probes:\n\n`metric[failure]/(metric[failure]+metric[success])`\n\nLatency metrics between VMs\n---------------------------\n\nLatency metrics for a specific project are calculated as the round-trip time (RTT)\nfor the following resource type and metric:\n\n- Resource type: `gce_instance`\n- Metric: `networking.googleapis.com/vm_flow/rtt`\n- Description: A distribution of RTT measured over TCP connections between the local virtual machine (VM) instance.\n\nLatency metrics across all Google Cloud projects between zones are calculated as\nthe round-trip time (RTT) for the following resource type and metric [(Preview)](/products#product-launch-stages):\n\n- Resource type: `networking.googleapis.com/Location`\n- Metric: `networking.googleapis.com/all_gcp/vm_traffic/zone_pair_median_rtt`\n- Description: The median RTT (round-trip time) for VM-to-VM traffic, for each zone\n pair and aggregated across all Google Cloud projects.\n\n Ensure that the **Only show active resources and metrics** option is disabled\n when using the latency metric in [Dashboards](/monitoring/charts/dashboards)\n or [Metrics Explorer](/monitoring/charts/metrics-explorer) for each zone pair\n across all Google Cloud projects.\n\n You cannot query latency for each zone pair across all Google Cloud\n projects using Monitoring Query Language (MQL).\n\nLatency metrics between VMs and internet endpoints\n--------------------------------------------------\n\nLatency metrics are calculated as round-trip time (RTT) for the following\nresource and metric:\n\n- Resource: `gce_instance`\n- Metric: `networking.googleapis.com/vm_flow/external_rtt`\n- Description: A distribution of RTT measured over TCP connections between the local virtual machine (VM) instance and internet endpoints.\n\nCreate Monitoring custom dashboards\n-----------------------------------\n\nYou can create custom Monitoring dashboards for\nPerformance Dashboard metrics. For more information, see [Dashboards](/monitoring/dashboards).\n\nCreate a chart with Metrics Explorer\n------------------------------------\n\nYou can create a chart with Metrics Explorer for the latency metric for your\nproject. For more information, see [Metrics explorer](/monitoring/charts/metrics-explorer).\n\nCreate a metric-based alerting policy\n-------------------------------------\n\nYou can create a metric-based alerting policy on the latency metric for your\nproject. For more information, see [Alerts](/monitoring/alerts).\n\nMonitor network performance for multiple projects\n-------------------------------------------------\n\nIf you prefer to monitor multiple projects in a single view, you can\nuse Cloud Monitoring or add projects to a metrics scope.\n\nWhen you access Cloud Monitoring for your Google Cloud project, by default you\nhave access to the metrics for your selected project. However, you\ncan configure Cloud Monitoring to view metrics for up to 375\nGoogle Cloud projects. For more details, see [Monitored project limits](/monitoring/quotas#workspace_limits).\n\nFor more information, see\n[Configuring your project for Cloud Monitoring](/monitoring/settings).\n\nChange project scope\n--------------------\n\nTo view multiple projects in Performance Dashboard, 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 projects\nin a single view, select the scoping project by using the Google Cloud console\nproject picker or the **Change Scope** button. You can also use these options to\nselect a single monitoring project.\n\nWhat's next\n-----------\n\n- [View project-specific packet loss dashboard](/network-intelligence-center/docs/performance-dashboard/how-to/view-project-specific-packet-loss)\n- [View Google Cloud packet loss dashboard](/network-intelligence-center/docs/performance-dashboard/how-to/view-google-cloud-packet-loss)\n- [View project-specific latency dashboard](/network-intelligence-center/docs/performance-dashboard/how-to/view-project-specific-latency)\n- [View Google Cloud latency metrics](/network-intelligence-center/docs/performance-dashboard/how-to/view-google-cloud-latency)\n- [View Performance Dashboard metrics in the Google Cloud console](/network-intelligence-center/docs/performance-dashboard/how-to/using-performance-dashboard)\n- [Troubleshoot Performance Dashboard](/network-intelligence-center/docs/performance-dashboard/support/troubleshooting)"]]
