Skip to content

Commit d7b0f80

Browse files
authored
Merge pull request #86098 from vhorne/ag-faq
add nsg flow logs
2 parents 41e4989 + b055543 commit d7b0f80

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

articles/application-gateway/application-gateway-faq.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,7 @@ services: application-gateway
55
author: vhorne
66
ms.service: application-gateway
77
ms.topic: article
8-
ms.workload: infrastructure-services
9-
ms.date: 6/1/2019
8+
ms.date: 08/22/2019
109
ms.author: victorh
1110
---
1211

@@ -357,6 +356,13 @@ You can also use a Resource Manager template that installs and runs the popular
357356

358357
Usually, you see an unknown status when access to the backend is blocked by a network security group (NSG), custom DNS, or user-defined routing (UDR) on the application gateway subnet. For more information, see [Backend health, diagnostics logging, and metrics for Application Gateway](application-gateway-diagnostics.md).
359358

359+
### Is there any case where NSG flow logs won't show allowed traffic?
360+
361+
Yes. If your configuration matches following scenario, you won't see allowed traffic in your NSG flow logs:
362+
- You've deployed Application Gateway v2
363+
- You have an NSG on the application gateway subnet
364+
- You've enabled NSG flow logs on that NSG
365+
360366
## Next steps
361367

362368
To learn more about Application Gateway, see [What is Azure Application Gateway?](overview.md).

0 commit comments

Comments
 (0)