mirror of
https://github.com/langgenius/dify-docs.git
synced 2026-03-26 13:18:34 +07:00
fix: avoid non-existent variables (#703)
This commit is contained in:
@@ -61,7 +61,7 @@ Once successfully saved, you can view the monitoring status on the current page.
|
||||
<td>- placed in metadata</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>workflow\_{id}</td>
|
||||
<td>{"workflow_{id}"}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
@@ -83,7 +83,7 @@ After configuration, debugging or production data of the application in Dify can
|
||||
<td>user\_id</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>workflow\_{id}</td>
|
||||
<td>{"workflow_{id}"}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -186,7 +186,7 @@ After configuration, debugging or production data of the application in Dify can
|
||||
<td>user\_id</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>message\_{id}</td>
|
||||
<td>{"message_{id}"}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
@@ -101,7 +101,7 @@ Detailed LLM operation logs through LangSmith will help you optimize the perform
|
||||
<td>- placed in metadata</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>workflow\_{id}</td>
|
||||
<td>{"workflow_{id}"}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -200,7 +200,7 @@ Detailed LLM operation logs through LangSmith will help you optimize the perform
|
||||
<td>- placed in metadata</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>“message\_{id}"</td>
|
||||
<td>{'"message_{id}"'}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
@@ -73,7 +73,7 @@ Detailed LLM operation logs through Opik will help you optimize the performance
|
||||
<td>- placed in metadata</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>workflow\_{id}</td>
|
||||
<td>{"workflow_{id}"}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
@@ -95,7 +95,7 @@ Once successfully saved, you can view the monitoring status on the current page.
|
||||
<td>- placed in metadata</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>workflow\_{id}</td>
|
||||
<td>{"workflow_{id}"}</td>
|
||||
<td>name</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
@@ -56,7 +56,7 @@ Detailed LLM operation logs through Weave will help you optimize the performance
|
||||
| ---------------------------------------- | ---------------------------- |
|
||||
| workflow_app_log_id/workflow_run_id | id |
|
||||
| user_session_id | placed in metadata |
|
||||
| workflow_{id} | name |
|
||||
| workflow_\{id\} | name |
|
||||
| start_time | start_time |
|
||||
| end_time | end_time |
|
||||
| inputs | inputs |
|
||||
@@ -109,7 +109,7 @@ Detailed LLM operation logs through Weave will help you optimize the performance
|
||||
| -------------------------------- | ---------------------------- |
|
||||
| message_id | id |
|
||||
| user_session_id | placed in metadata |
|
||||
| “message_{id}" | name |
|
||||
| "message_\{id\}" | name |
|
||||
| start_time | start_time |
|
||||
| end_time | end_time |
|
||||
| inputs | inputs |
|
||||
|
||||
@@ -25,7 +25,7 @@ POST {Your-API-Endpoint}
|
||||
| Header | Value | Desc |
|
||||
| --------------- | ----------------- | --------------------------------------------------------------------- |
|
||||
| `Content-Type` | application/json | The request content is in JSON format. |
|
||||
| `Authorization` | Bearer {api_key} | The API Key is transmitted as a Token. You need to parse the `api_key` and verify that it matches the provided API Key to ensure interface security. |
|
||||
| `Authorization` | Bearer \{api_key\} | The API Key is transmitted as a Token. You need to parse the `api_key` and verify that it matches the provided API Key to ensure interface security. |
|
||||
|
||||
### Request Body
|
||||
|
||||
|
||||
Reference in New Issue
Block a user