Skip to content

Commit 1ba3679

Browse files
Merge pull request #266498 from KazuOnuki/kazuyaonuki-patch2
Update how-to-monitor-online-endpoints.md
2 parents 2c7e817 + f02714b commit 1ba3679

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/machine-learning/how-to-monitor-online-endpoints.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ For more information, see [Create Azure Monitor alert rules](../azure-monitor/al
137137

138138
There are three logs that can be enabled for online endpoints:
139139

140-
* **AMLOnlineEndpointTrafficLog**: You could choose to enable traffic logs if you want to check the information of your request. Below are some cases:
140+
* **AmlOnlineEndpointTrafficLog**: You could choose to enable traffic logs if you want to check the information of your request. Below are some cases:
141141

142142
* If the response isn't 200, check the value of the column "ResponseCodeReason" to see what happened. Also check the reason in the "HTTPS status codes" section of the [Troubleshoot online endpoints](how-to-troubleshoot-online-endpoints.md#http-status-codes) article.
143143

@@ -147,17 +147,17 @@ There are three logs that can be enabled for online endpoints:
147147

148148
* If you want to check how many requests or failed requests recently. You could also enable the logs.
149149

150-
* **AMLOnlineEndpointConsoleLog**: Contains logs that the containers output to the console. Below are some cases:
150+
* **AmlOnlineEndpointConsoleLog**: Contains logs that the containers output to the console. Below are some cases:
151151

152152
* If the container fails to start, the console log can be useful for debugging.
153153

154154
* Monitor container behavior and make sure that all requests are correctly handled.
155155

156-
* Write request IDs in the console log. Joining the request ID, the AMLOnlineEndpointConsoleLog, and AMLOnlineEndpointTrafficLog in the Log Analytics workspace, you can trace a request from the network entry point of an online endpoint to the container.
156+
* Write request IDs in the console log. Joining the request ID, the AmlOnlineEndpointConsoleLog, and AmlOnlineEndpointTrafficLog in the Log Analytics workspace, you can trace a request from the network entry point of an online endpoint to the container.
157157

158158
* You can also use this log for performance analysis in determining the time required by the model to process each request.
159159

160-
* **AMLOnlineEndpointEventLog**: Contains event information regarding the container's life cycle. Currently, we provide information on the following types of events:
160+
* **AmlOnlineEndpointEventLog**: Contains event information regarding the container's life cycle. Currently, we provide information on the following types of events:
161161

162162
| Name | Message |
163163
| ----- | ----- |
@@ -209,15 +209,15 @@ You can find example queries on the __Queries__ tab while viewing logs. Search f
209209

210210
The following tables provide details on the data stored in each log:
211211

212-
**AMLOnlineEndpointTrafficLog**
212+
**AmlOnlineEndpointTrafficLog**
213213

214214
[!INCLUDE [endpoint-monitor-traffic-reference](includes/endpoint-monitor-traffic-reference.md)]
215215

216-
**AMLOnlineEndpointConsoleLog**
216+
**AmlOnlineEndpointConsoleLog**
217217

218218
[!INCLUDE [endpoint-monitor-console-reference](includes/endpoint-monitor-console-reference.md)]
219219

220-
**AMLOnlineEndpointEventLog**
220+
**AmlOnlineEndpointEventLog**
221221

222222
[!INCLUDE [endpoint-monitor-event-reference](includes/endpoint-monitor-event-reference.md)]
223223

0 commit comments

Comments
 (0)