運用分割記錄檔處理長時間的記錄項目
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Cloud Logging 會將傳入記錄的大小限制為 256 KB，並捨棄任何較大的記錄。為確保 Cloud Logging 保留大型記錄，Fleet Engine 會將其分割成一系列較小的記錄。
雲端記錄可能會分割 Fleet Engine 的下列記錄：
每個分割記錄項目都包含下列欄位：
split.uid：從常見原始記錄項目分割出來的記錄項目群組專屬 ID。從原始記錄項目分割的所有項目，這個欄位的值都相同。split.index：這個項目在分割項目序列中的位置。分割的第一個項目索引為 0.split.index。這個索引也會附加至 LogEntry.insertId 欄位。split.totalSplits：原始記錄項目分割成的記錄項目數量。從原始記錄項目分割的所有項目，這個欄位的值都相同。
split log 1:
insertId: "XXXX-01"
split {index: 0, uuid: "XXXX"}
splitLog 2:
insertId: "XXX-02"
split {index: 1, uuid: "XXXX"}
如要找出從特定記錄分割的所有記錄，請使用類似以下的查詢：
split.uid="789+2022-02-22T12:22:22.22+05:00"
sortby split.index OR sortby insertID
這些分割記錄的結構與 Cloud 稽核記錄指南中顯示的結構幾乎相同。主要差異在於 Fleet Engine 記錄的分割作業是在 jsonPayload 欄位中進行。如需詳細資訊和範例，請參閱分割稽核記錄項目。
後續步驟
如要根據條件計算及篩選記錄，請建立記錄指標。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-09-05 (世界標準時間)。
[null,null,["上次更新時間：2025-09-05 (世界標準時間)。"],[[["\u003cp\u003eCloud Logging limits log size to 256KB, and Fleet Engine can split larger logs into smaller segments for retention.\u003c/p\u003e\n"],["\u003cp\u003eSplit logs contain unique identifiers (\u003ccode\u003esplit.uid\u003c/code\u003e), index (\u003ccode\u003esplit.index\u003c/code\u003e), and total split count (\u003ccode\u003esplit.totalSplits\u003c/code\u003e) for reassembly.\u003c/p\u003e\n"],["\u003cp\u003eYou can search for related split logs using the \u003ccode\u003esplit.uid\u003c/code\u003e and sort by \u003ccode\u003esplit.index\u003c/code\u003e or \u003ccode\u003einsertId\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eFleet Engine's split log structure is similar to Cloud Audit Logs, with splitting occurring in the \u003ccode\u003ejsonPayload\u003c/code\u003e field.\u003c/p\u003e\n"]]],[],null,["Cloud Logging limits the size on incoming logs to 256KB and drops\nanything bigger. To ensure that Cloud Logging retains your large\nlogs, Fleet Engine can split them into a series of smaller logs.\n\nCloud logging may split the following logs from Fleet Engine:\n\n- [SearchVehiclesLog](/maps/documentation/mobility/operations/cloud-logging/reference/trips/rest/Shared.Types/SearchVehiclesLog)\n- [ListDeliveryVehicle](/maps/documentation/mobility/operations/cloud-logging/reference/tasks/rest/Shared.Types/ListDeliveryVehiclesLog)\n- [ListTasksLog](/maps/documentation/mobility/operations/cloud-logging/reference/tasks/rest/Shared.Types/ListTasksLog)\n- [BatchCreateTasksLog](/maps/documentation/mobility/operations/cloud-logging/reference/tasks/rest/Shared.Types/BatchCreateTasksLog)\n\nEach split log entry contains the following fields:\n\n- `split.uid`: A unique identifier for the group of log entries that were split from a common original log entry. The value of this field is the same for all entries split from the original log entry.\n- `split.index`: The position of this entry in the series of split entries. The first entry from the split has index `0.split.index`. This index is also appended to the `LogEntry.insertId` field.\n- `split.totalSplits`: The number of log entries that the original log entry was split into. The value of this field is the same for all entries split from the original log entry.\n\n split log 1:\n insertId: \"XXXX-01\"\n split {index: 0, uuid: \"XXXX\"}\n\n splitLog 2:\n insertId: \"XXX-02\"\n split {index: 1, uuid: \"XXXX\"}\n\nTo find all the logs that were split from one specific log, use a query like: \n\n split.uid=\"789+2022-02-22T12:22:22.22+05:00\"\n sortby split.index OR sortby insertID\n\nThe structure of these split logs is almost the same as the structure shown in\nthe guide for Cloud Audit Logs. The major difference is that for Fleet Engine\nlogs, the split occurs in the `jsonPayload` field. For details and examples, see\n[Split audit log entries](https://cloud.google.com/logging/docs/audit/split-logs).\n\nWhat's next\n\nTo count and filter logs according to you criteria, [create log-based\nmetrics](/maps/documentation/mobility/operations/cloud-logging/metrics)."]]
