[[["易于理解","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-18。"],[[["\u003cp\u003eDialogflow API requests and responses can be optionally logged to Cloud Logging for your agent, which can be enabled or disabled in the agent's general settings.\u003c/p\u003e\n"],["\u003cp\u003eOnce enabled, logs can be viewed using the Cloud Logs Explorer, and log entry titles include Dialogflow Request, Response, webhook request, webhook response, and webhook error.\u003c/p\u003e\n"],["\u003cp\u003eThe content of the \u003ccode\u003ejsonPayload\u003c/code\u003e field within request and response log entries resembles the structure of corresponding Dialogflow API REST requests and responses.\u003c/p\u003e\n"],["\u003cp\u003eBy default, Dialogflow Cloud log entries are routed to the global _Default logs bucket, but they can be directed to a region-specific bucket to meet data residency requirements.\u003c/p\u003e\n"],["\u003cp\u003eIf a Dialogflow response is too big, the \u003ccode\u003eQueryResult.diagnosticInfo\u003c/code\u003e field is omitted from the Cloud logging logs, and at most 500 turns will be logged per conversation.\u003c/p\u003e\n"]]],[],null,["# Cloud logging\n\nDialogflow API requests and responses can optionally be logged to\n[Cloud logging](/logging/docs)\nfor your agent.\nYou can also control the\n\n[region](/dialogflow/cx/docs/concept/region)\n\nin which these logs are stored.\n\nEnable Cloud logging\n--------------------\n\nTo enable or disable Cloud logging for your agent,\nsee the logging options in the\n\n[agent's general settings](/dialogflow/cx/docs/concept/agent#settings-general).\n\n\nViewing Cloud logs\n------------------\n\nOnce you enable Cloud logging for an agent,\nyou can browse these logs using the\n[Cloud Logs Explorer](/logging/docs/view/logs-explorer-interface).\n\nLog format\n----------\n\nFor detailed information on the log format, see\n[Log entry structure](/logging/docs/api/platform-logs#structure).\n\nThe following is a partial list of log entry titles used by Dialogflow:\n\n- Dialogflow Request\n- Dialogflow Response\n- Dialogflow webhook request\n- Dialogflow webhook response\n- Dialogflow webhook error\n\nRequest and response log entries have a `jsonPayload` field in the JSON format. The content of this payload resembles the structure of like-named Dialogflow API REST requests and responses as defined in [Dialogflow reference documentation](/dialogflow/cx/docs/reference).\n\nRegionalization\n---------------\n\nBy default, Dialogflow Cloud log entries are routed to the\n[_Default logs bucket](/logging/docs/buckets),\nwhich is global.\nIf you have data residency requirements for your project,\nyou can route your logs to a region-specific logs bucket.\nFor instructions, see\n[regionalizing your project's logs using logs buckets](/logging/docs/regionalized-logs).\n| **Note:** When redirecting log sinks, you can use \n| `LOG_ID(\"dialogflow-runtime.googleapis.com/requests\")` for filtering Dialogflow Cloud logs.\n\nLimitations\n-----------\n\nIf Dialogflow response exceeds the Cloud logging log entry size\n[limit](/logging/quotas), the `QueryResult.diagnosticInfo` field is not included\nin the logs.\n\nAt most 500 turns will be logged for each conversation."]]
