You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-monitor-online-endpoints.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,7 +137,7 @@ For more information, see [Create Azure Monitor alert rules](../azure-monitor/al
137
137
138
138
There are three logs that can be enabled for online endpoints:
139
139
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:
141
141
142
142
* 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.
143
143
@@ -147,17 +147,17 @@ There are three logs that can be enabled for online endpoints:
147
147
148
148
* If you want to check how many requests or failed requests recently. You could also enable the logs.
149
149
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:
151
151
152
152
* If the container fails to start, the console log can be useful for debugging.
153
153
154
154
* Monitor container behavior and make sure that all requests are correctly handled.
155
155
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.
157
157
158
158
* You can also use this log for performance analysis in determining the time required by the model to process each request.
159
159
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:
161
161
162
162
| Name | Message |
163
163
| ----- | ----- |
@@ -209,15 +209,15 @@ You can find example queries on the __Queries__ tab while viewing logs. Search f
209
209
210
210
The following tables provide details on the data stored in each log:
0 commit comments