Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 17899a7

Browse files
committedJan 24, 2022
update image and remove View and analyze section
1 parent 8a7eda4 commit 17899a7

File tree

3 files changed

+5
-31
lines changed

3 files changed

+5
-31
lines changed
 

‎articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md

Lines changed: 5 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: Troubleshoot session affinity issues
33
titleSuffix: Azure Application Gateway
44
description: This article provides information on how to troubleshoot session affinity issues in Azure Application Gateway
55
services: application-gateway
6-
author: KumudD
6+
author: vhorne
77
ms.service: application-gateway
88
ms.topic: troubleshooting
9-
ms.date: 01/21/2022
10-
ms.author: kumud
9+
ms.date: 01/24/2022
10+
ms.author: victorh
1111
---
1212

1313
# Troubleshoot Azure Application Gateway session affinity issues
@@ -44,9 +44,9 @@ Sometimes the session affinity issues might occur when you forget to enable “C
4444

4545
![Screenshot shows SETTINGS with H T T P settings selected.](./media/how-to-troubleshoot-application-gateway-session-affinity-issues/troubleshoot-session-affinity-issues-1.png)
4646

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.
4848

49-
![Screenshot shows the gateway settings for an app gateway, inlcuidng whether Cookie based affinity is selected.](./media/how-to-troubleshoot-application-gateway-session-affinity-issues/troubleshoot-session-affinity-issues-2.jpg)
49+
![Screenshot shows the gateway settings for an app gateway, including whether Cookie based affinity is selected.](./media/how-to-troubleshoot-application-gateway-session-affinity-issues/troubleshoot-session-affinity-issues-2.png)
5050

5151

5252

@@ -122,33 +122,7 @@ Enable logging using the Azure portal.
122122
4. Confirm the settings and then select **Save**.
123123

124124

125-
#### View and analyze the Application Gateway access logs
126125

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-
![Screenshot shows the Log categories dropdown list with ApplicationGatewayAccessLog selected.](./media/how-to-troubleshoot-application-gateway-session-affinity-issues/troubleshoot-session-affinity-issues-9.png)
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-
![Screenshot shows server status in plain text, mostly obscured, with clientPort and SERVER-ROUTED highlighted.](./media/how-to-troubleshoot-application-gateway-session-affinity-issues/troubleshoot-session-affinity-issues-11.png)
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.
152126

153127
### Use web debugger to capture and analyze the HTTP or HTTPS traffics
154128

0 commit comments

Comments
 (0)
Please sign in to comment.