在 Flow Analyzer 中排解資料問題
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
請參考以下指南,排解 Flow Analyzer 的常見問題。如要進一步瞭解 Flow Analyzer,請參閱總覽。
未顯示任何資料
如果在 Flow Analyzer 中沒有看到任何資料,請執行下列操作:
- 請確認已為相關子網路啟用虛擬私有雲流量記錄。詳情請參閱「在建立子網路時啟用虛擬私有雲流量記錄」或「針對現有子網路啟用虛擬私有雲流量記錄」。
- 請確認時間軸設定正確無誤。如果所選時間範圍內沒有流量,Flow Analyzer 就不會顯示任何資料。詳情請參閱「時間範圍選取器」。
- 驗證記錄檔值區設定:
- 請確認專案有包含虛擬私有雲流量記錄檔的記錄值區。
- 確認專案中的記錄值區並未停用虛擬私有雲流量記錄檔。
- 確認虛擬私有雲流量記錄檔不會導向其他值區。詳情請參閱「設定中央儲存桶」。
- 確認記錄檔值區已升級,可使用 Log Analytics。詳情請參閱「啟用 Log Analytics」。
- 檢查是否缺少欄位和篩選器:
- 請確認取樣率不會過低。
虛擬私有雲流量記錄中沒有任何中繼資料欄位,原因如下:
- 這個專案的 VPC Flow Logs 已停用中繼資料。
- 流量方向是跨專案通訊的一部分。
- 實際資料不明,因為流量來自外部資源。
- 尚未提供中繼資料資訊。
在虛擬私有雲流量記錄中篩除的欄位
啟用 VPC 流量記錄後,您可以根據基礎和中繼資料欄位設定篩選器,只保留符合篩選條件的記錄。所有其他記錄都會在寫入 Logging 前遭到捨棄,這麼做可節省您的金錢,並縮短您尋找所需資訊所需的時間。
您或其他使用者可以依據記錄格式的任何子集欄位進行篩選。請確認專案中的其他使用者不會篩除必填欄位。詳情請參閱「篩選記錄」。
取樣率偏低
如果取樣率設定得太低,您就無法在 Flow Analyzer 中查看任何資料。
如需其他疑難排解資訊,請參閱「排解虛擬私有雲端流量記錄問題」。
提供 Flow Analyzer 相關意見
如要提供有關 Flow Analyzer 的意見回饋,或是在使用 Flow Analyzer 時遇到任何問題,請按照下列步驟操作:
- 按一下「提供意見」圖示。畫面隨即顯示「Send feedback to Google」(傳送意見回饋給 Google) 面板。
- 請提供意見回饋。
- 如要新增螢幕截圖,請按一下「擷取螢幕截圖」。你也可以使用「編輯」工具標示有疑慮之處或隱藏機密資訊。
- 選取目前分頁的內容。
- 按一下「分享」。螢幕截圖已加入意見回饋中。
- 按一下 [傳送]。
後續步驟
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-09-04 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Troubleshoot data issues in Flow Analyzer\n\nUse the following guidance to troubleshoot common issues with\nFlow Analyzer. To learn more about Flow Analyzer, see the\n[overview](/network-intelligence-center/docs/flow-analyzer/overview).\n\nNo data is displayed\n--------------------\n\nIf you don't see any data in Flow Analyzer, do the following:\n\n1. Make sure that VPC Flow Logs is enabled for the relevant subnets. For more information, see [Enable VPC Flow Logs when you create a subnet](/vpc/docs/using-flow-logs#enable-logging-new) or [Enable VPC Flow Logs for an existing subnet](/vpc/docs/using-flow-logs#enable-logging-existing).\n2. Make sure that the timeline is correctly set. If there's no traffic flow within the selected time period, Flow Analyzer doesn't show any data. For more information, see [Time-range selector](/network-intelligence-center/docs/flow-analyzer/overview#time-selector).\n3. Validate the log bucket setup:\n - Ensure that the project has a log bucket that contains VPC Flow Logs.\n - Check that VPC Flow Logs is not disabled for the log bucket in the project.\n - Verify that VPC Flow Logs is not directed to another bucket. For more information, see [Configure a central bucket](/network-intelligence-center/docs/flow-analyzer/configure-central-bucket).\n - Confirm that the log bucket is upgraded to use Log Analytics. For more information, see [Enable Log Analytics](/network-intelligence-center/docs/flow-analyzer/enable-log-analytics).\n4. Check for missing fields and filters:\n - Make sure that there are no [missing metadata fields](#missing-metadata).\n - Verify there are no [filtered out fields in VPC Flow Logs](#filtered-out-fields).\n5. Make sure that the [sampling rate is not too low](#low-sampling-rate).\n\nMissing metadata fields\n-----------------------\n\nThere aren't any metadata fields in VPC Flow Logs due to the\nfollowing reasons:\n\n- Metadata is disabled in VPC Flow Logs for this project.\n- The traffic flow is a part of cross-project communication.\n- Actual data is unknown because the traffic is from an external resource.\n- The metadata information is not yet available.\n\nFiltered out fields in VPC Flow Logs\n------------------------------------\n\nWhen you enable VPC Flow Logs, you can set a filter based on both base and\nmetadata fields that only preserves logs that match the filter. All other logs\nare discarded before being written to Logging, which saves you\nmoney and reduces the time needed to find the information you are looking for.\n\nYou or other users can filter on any subset of fields from the\nrecord format. Verify that the required fields are not filtered out by other users\nin your project. For more information, see\n[Log filtering](/vpc/docs/about-flow-logs-records#filtering).\n\nLow sampling rate\n-----------------\n\nIf the sampling rate is set too low, you cannot see any data in\nFlow Analyzer.\n\nFor additional troubleshooting information, see\n[Troubleshoot VPC Flow Logs](/vpc/docs/access-flow-logs#troubleshooting).\n\nSend feedback about Flow Analyzer\n---------------------------------\n\nTo send your feedback about Flow Analyzer or any issues faced\nwhile using Flow Analyzer, do the following:\n\n1. Click the **Send feedback** icon. The Send feedback to Google panel appears.\n2. Describe your feedback.\n3. To add a screenshot, click **Capture screenshot** . You can also mark the area of concern or hide sensitive information by using the **Edit** tool.\n4. Select the contents of the current tab.\n5. Click **Share**. The screenshot is added to the feedback.\n6. Click **Send**.\n\nWhat's next\n-----------\n\n- [Analyze traffic flows](/network-intelligence-center/docs/flow-analyzer/analyze-traffic-flows)\n- [Run Connectivity Tests from Flow Analyzer](/network-intelligence-center/docs/flow-analyzer/run-connectivity-tests)\n- [Monitor your traffic flows](/network-intelligence-center/docs/flow-analyzer/monitor-traffic-flows)"]]