在哪里查看 watson assistant 错误日志
Where to view watson assistant error logs
webhook 调用失败,如何查看详细日志?
testing webhooks页面描述错误放在output.webhook_error.<result_variable>
中。例如,如果您的结果变量是 webhook_result_1
那么输出是 output.webhook_error.webhook_result_1
.
如文档中所述,如果在对话节点编辑器的“助手响应”部分发生错误,则应使用“如果助手识别”anything_else
,因此您可以将其放入The callout generated this error: <? output.webhook_error.webhook_result_1 ?>.
.
这将显示更多信息。例如,如果我配置一个 API 来抛出错误,我将返回:
The callout generated this error: {"response_code":400,"message":"Webhook call was not successful. Response code is [400].","response_body":{"code":"cff11d18150e8018d5e304ac3fc35c94","error":"There was an error processing your request."},"content_type":"application/json"}.
如果在实时使用 Bot 时发生此错误,则会在日志中捕获 webhook 响应正文。如果您使用 UI 中的“试用”面板,则 不会 捕获日志。
在分析选项卡中技能的助手 UI 中显示对话。在 UI 的“用户对话”部分,对话的文本被捕获,但如果您按上述方式添加输出,您将只会看到 webhooks 错误。
API 可用于获取工作区或技能的日志,其中包含 webhook 错误详细信息。参见 List Log Events in a Workspace。如果您正在使用技能,那么您可以从助手 UI 中找到要使用的 URL。在技能列表页面上,在特定技能上单击 ...
菜单和 select 查看 API 详细信息。 Legacy v1 workspace URL:
显示要使用的工作区 ID。
例如,如果 Legacy v1 workspace URL:
是 https://gateway.watsonplatform.net/assistant/api/v1/workspaces/ce13f844-c3a7-4f36-97c6-a0ac704024a6/message
,则用于获取日志的 URL 是 https://gateway.watsonplatform.net/assistant/api/v1/workspaces/ce13f844-c3a7-4f36-97c6-a0ac704024a6/logs?version=2020-04-01
在工作区日志中,将包含 webhook_error
中发生 webhook 错误的用户对话的详细信息:
"output": {
"generic": [
{
"response_type": "text",
"text": ""
},
{
"response_type": "text",
"text": "The callout generated this error: {\"response_code\":400,\"message\":\"Webhook call was not successful. Response code is [400].\",\"response_body\":{\"code\":\"cff11d18150e8018d5e304ac3fc35c94\",\"error\":\"There was an error processing your request.\"},\"content_type\":\"application/json\"}."
},
{
"response_type": "text",
"text": "Customer email is <? context.webhook_result_1.message ?>."
}
],
"text": [
"",
"The callout generated this error: {\"response_code\":400,\"message\":\"Webhook call was not successful. Response code is [400].\",\"response_body\":{\"code\":\"cff11d18150e8018d5e304ac3fc35c94\",\"error\":\"There was an error processing your request.\"},\"content_type\":\"application/json\"}.",
"Customer email is <? context.webhook_result_1.message ?>."
],
"nodes_visited": [
"slot_2_1520179906877",
"handler_3_1520179906877",
"node_1_1520179877410",
"node_9_1530805081298",
"response_5_1604940050659",
"node_7_1520180645829"
],
"webhook_error": {
"webhook_result_1": {
"response_code": 400,
"message": "Webhook call was not successful. Response code is [400].",
"response_body": {
"code": "cff11d18150e8018d5e304ac3fc35c94",
"error": "There was an error processing your request."
},
"content_type": "application/json"
}
},
"nodes_visited_details": [
webhook 调用失败,如何查看详细日志?
testing webhooks页面描述错误放在output.webhook_error.<result_variable>
中。例如,如果您的结果变量是 webhook_result_1
那么输出是 output.webhook_error.webhook_result_1
.
如文档中所述,如果在对话节点编辑器的“助手响应”部分发生错误,则应使用“如果助手识别”anything_else
,因此您可以将其放入The callout generated this error: <? output.webhook_error.webhook_result_1 ?>.
.
这将显示更多信息。例如,如果我配置一个 API 来抛出错误,我将返回:
The callout generated this error: {"response_code":400,"message":"Webhook call was not successful. Response code is [400].","response_body":{"code":"cff11d18150e8018d5e304ac3fc35c94","error":"There was an error processing your request."},"content_type":"application/json"}.
如果在实时使用 Bot 时发生此错误,则会在日志中捕获 webhook 响应正文。如果您使用 UI 中的“试用”面板,则 不会 捕获日志。
在分析选项卡中技能的助手 UI 中显示对话。在 UI 的“用户对话”部分,对话的文本被捕获,但如果您按上述方式添加输出,您将只会看到 webhooks 错误。
API 可用于获取工作区或技能的日志,其中包含 webhook 错误详细信息。参见 List Log Events in a Workspace。如果您正在使用技能,那么您可以从助手 UI 中找到要使用的 URL。在技能列表页面上,在特定技能上单击 ...
菜单和 select 查看 API 详细信息。 Legacy v1 workspace URL:
显示要使用的工作区 ID。
例如,如果 Legacy v1 workspace URL:
是 https://gateway.watsonplatform.net/assistant/api/v1/workspaces/ce13f844-c3a7-4f36-97c6-a0ac704024a6/message
,则用于获取日志的 URL 是 https://gateway.watsonplatform.net/assistant/api/v1/workspaces/ce13f844-c3a7-4f36-97c6-a0ac704024a6/logs?version=2020-04-01
在工作区日志中,将包含 webhook_error
中发生 webhook 错误的用户对话的详细信息:
"output": {
"generic": [
{
"response_type": "text",
"text": ""
},
{
"response_type": "text",
"text": "The callout generated this error: {\"response_code\":400,\"message\":\"Webhook call was not successful. Response code is [400].\",\"response_body\":{\"code\":\"cff11d18150e8018d5e304ac3fc35c94\",\"error\":\"There was an error processing your request.\"},\"content_type\":\"application/json\"}."
},
{
"response_type": "text",
"text": "Customer email is <? context.webhook_result_1.message ?>."
}
],
"text": [
"",
"The callout generated this error: {\"response_code\":400,\"message\":\"Webhook call was not successful. Response code is [400].\",\"response_body\":{\"code\":\"cff11d18150e8018d5e304ac3fc35c94\",\"error\":\"There was an error processing your request.\"},\"content_type\":\"application/json\"}.",
"Customer email is <? context.webhook_result_1.message ?>."
],
"nodes_visited": [
"slot_2_1520179906877",
"handler_3_1520179906877",
"node_1_1520179877410",
"node_9_1530805081298",
"response_5_1604940050659",
"node_7_1520180645829"
],
"webhook_error": {
"webhook_result_1": {
"response_code": 400,
"message": "Webhook call was not successful. Response code is [400].",
"response_body": {
"code": "cff11d18150e8018d5e304ac3fc35c94",
"error": "There was an error processing your request."
},
"content_type": "application/json"
}
},
"nodes_visited_details": [