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
@@ -44,9 +44,9 @@ Sometimes the session affinity issues might occur when you forget to enable “C
44
44
45
45

46
46
47
-
4.Click **appGatewayBackendHttpSettings** on the right side to check whether you have selected **Enabled** for Cookie based affinity.
47
+
4.Select the HTTP setting, and on the **Add HTTP setting** page, check if **Cookie based affinity** is enabled.
48
48
49
-

49
+

50
50
51
51
52
52
@@ -122,33 +122,7 @@ Enable logging using the Azure portal.
122
122
4. Confirm the settings and then select **Save**.
123
123
124
124
125
-
#### View and analyze the Application Gateway access logs
126
125
127
-
1. In the Azure portal under the Application Gateway resource view, select **Diagnostics settings** in the **Monitoring** section.
128
-
129
-
2. On the right side, select “**ApplicationGatewayAccessLog**“ in the drop-down list under **Log categories.**
130
-
131
-

132
-
133
-
3. In the Application Gateway Access Log list, click the log you want to analyze and export, and then export the JSON file.
134
-
135
-
4. Convert the JSON file that you exported in step 3 to CSV file and view them in Excel, Power BI, or any other data-visualization tool.
136
-
137
-
5. Check the following data:
138
-
139
-
-**ClientIP**– This is the client IP address from the connecting client.
140
-
-**ClientPort** - This is the source port from the connecting client for the request.
141
-
-**RequestQuery** – This indicates the destination server that the request is received.
142
-
-**Server-Routed**: Back-end pool instance that the request is received.
143
-
-**X-AzureApplicationGateway-LOG-ID**: Correlation ID used for the request. It can be used to troubleshoot traffic issues on the back-end servers. For example: X-AzureApplicationGateway-CACHE-HIT=0&SERVER-ROUTED=10.0.2.4.
144
-
145
-
-**SERVER-STATUS**: HTTP response code that Application Gateway received from the back end.
146
-
147
-

148
-
149
-
If you see two items are coming from the same ClientIP and Client Port, and they are sent to the same back-end server, that means the Application Gateway configured correctly.
150
-
151
-
If you see two items are coming from the same ClientIP and Client Port, and they are sent to the different back-end servers, that means the request is bouncing between backend servers, select “**Application is using cookie-based affinity but requests still bouncing between back-end servers**” at the bottom to troubleshoot it.
152
126
153
127
### Use web debugger to capture and analyze the HTTP or HTTPS traffics
0 commit comments