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/application-gateway/application-gateway-diagnostics.md
+47-46Lines changed: 47 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,57 +155,12 @@ Azure generates the activity log by default. The logs are preserved for 90 days
155
155
156
156
The access log is generated only if you've enabled it on each Application Gateway instance, as detailed in the preceding steps. The data is stored in the storage account that you specified when you enabled the logging. Each access of Application Gateway is logged in JSON format as shown below.
157
157
158
-
#### For Application Gateway Standard and WAF SKU (v1)
159
-
160
-
|Value |Description |
161
-
|---------|---------|
162
-
|instanceId | Application Gateway instance that served the request. |
163
-
|clientIP | Originating IP for the request. |
164
-
|clientPort | Originating port for the request. |
165
-
|httpMethod | HTTP method used by the request. |
166
-
|requestUri | URI of the received request. |
167
-
|RequestQuery | **Server-Routed**: Backend pool instance that was sent the request.</br>**X-AzureApplicationGateway-LOG-ID**: Correlation ID used for the request. It can be used to troubleshoot traffic issues on the backend servers. </br>**SERVER-STATUS**: HTTP response code that Application Gateway received from the back end. |
168
-
|UserAgent | User agent from the HTTP request header. |
169
-
|httpStatus | HTTP status code returned to the client from Application Gateway. |
170
-
|httpVersion | HTTP version of the request. |
171
-
|receivedBytes | Size of packet received, in bytes. |
172
-
|sentBytes| Size of packet sent, in bytes.|
173
-
|timeTaken| Length of time (in milliseconds) that it takes for a request to be processed and its response to be sent. This is calculated as the interval from the time when Application Gateway receives the first byte of an HTTP request to the time when the response send operation finishes. It's important to note that the Time-Taken field usually includes the time that the request and response packets are traveling over the network. |
174
-
|sslEnabled| Whether communication to the backend pools used TLS/SSL. Valid values are on and off.|
175
-
|host| The hostname with which the request has been sent to the backend server. If backend hostname is being overridden, this name will reflect that.|
176
-
|originalHost| The hostname with which the request was received by the Application Gateway from the client.|
|instanceId | Application Gateway instance that served the request. |
208
-
|clientIP |Originating IP for the request. |
163
+
|clientIP | IP of the immediate client of Application Gateway. If another proxy fronts your application gateway, this displays the IP of that fronting proxy. |
209
164
|httpMethod | HTTP method used by the request. |
210
165
|requestUri | URI of the received request. |
211
166
|UserAgent | User agent from the HTTP request header. |
@@ -273,6 +228,52 @@ The access log is generated only if you've enabled it on each Application Gatewa
273
228
> [!Note]
274
229
>Access logs with clientIP value 127.0.0.1 originate from an internal security process running on the application gateway instances. You can safely ignore these log entries.
275
230
231
+
#### For Application Gateway Standard and WAF SKU (v1)
232
+
233
+
|Value |Description |
234
+
|---------|---------|
235
+
|instanceId | Application Gateway instance that served the request. |
236
+
|clientIP | Originating IP for the request. |
237
+
|clientPort | Originating port for the request. |
238
+
|httpMethod | HTTP method used by the request. |
239
+
|requestUri | URI of the received request. |
240
+
|RequestQuery |**Server-Routed**: Backend pool instance that was sent the request.</br>**X-AzureApplicationGateway-LOG-ID**: Correlation ID used for the request. It can be used to troubleshoot traffic issues on the backend servers. </br>**SERVER-STATUS**: HTTP response code that Application Gateway received from the back end. |
241
+
|UserAgent | User agent from the HTTP request header. |
242
+
|httpStatus | HTTP status code returned to the client from Application Gateway. |
243
+
|httpVersion | HTTP version of the request. |
244
+
|receivedBytes | Size of packet received, in bytes. |
245
+
|sentBytes| Size of packet sent, in bytes.|
246
+
|timeTaken| Length of time (in milliseconds) that it takes for a request to be processed and its response to be sent. This is calculated as the interval from the time when Application Gateway receives the first byte of an HTTP request to the time when the response send operation finishes. It's important to note that the Time-Taken field usually includes the time that the request and response packets are traveling over the network. |
247
+
|sslEnabled| Whether communication to the backend pools used TLS/SSL. Valid values are on and off.|
248
+
|host| The hostname with which the request has been sent to the backend server. If backend hostname is being overridden, this name will reflect that.|
249
+
|originalHost| The hostname with which the request was received by the Application Gateway from the client.|
The performance log is generated only if you have enabled it on each Application Gateway instance, as detailed in the preceding steps. The data is stored in the storage account that you specified when you enabled the logging. The performance log data is generated in 1-minute intervals. It is available only for the v1 SKU. For the v2 SKU, use [Metrics](application-gateway-metrics.md) for performance data. The following data is logged:
0 commit comments