From 897a9f0ee9136e359927de27fe2bdf0995bf5a44 Mon Sep 17 00:00:00 2001 From: rishisingh0722 Date: Fri, 24 Oct 2025 15:32:10 +1100 Subject: [PATCH 1/2] add note about importance of checking Application Gateway Activity Logs Most users often overlook checking the Application Gateway Activity Logs. Adding this reminder helps users detect issues early by verifying AGIC configuration updates and operational events. --- .../application-gateway/ingress-controller-troubleshoot.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/articles/application-gateway/ingress-controller-troubleshoot.md b/articles/application-gateway/ingress-controller-troubleshoot.md index 33399a7d65bb3..89e4433219a17 100644 --- a/articles/application-gateway/ingress-controller-troubleshoot.md +++ b/articles/application-gateway/ingress-controller-troubleshoot.md @@ -312,3 +312,8 @@ rbac: aksClusterConfiguration: apiServerAddress: ``` + + +## Review Application Gateway Activity Log + +> When troubleshooting Application Gateway Ingress Controller issues, it's good practice to check the Application Gateway's Activity Log in addition to kubernetes resources. Every time AGIC applies a new configuration, a corresponding entry is recorded in the Activity Log in the Azure portal. Reviewing these entries helps to confirm whether configuration updates were successfully applied and can often reveals gateway-related issues that aren't visible from the kubernetes side. From b2cb104e2b55f8c17b42cce92fcadbedf79b85c2 Mon Sep 17 00:00:00 2001 From: rishisingh0722 Date: Mon, 27 Oct 2025 09:40:17 +1100 Subject: [PATCH 2/2] Fix typos in troubleshooting guide Corrected capitalization of 'Kubernetes' and fixed 'reveals' to 'reveal'. --- articles/application-gateway/ingress-controller-troubleshoot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/application-gateway/ingress-controller-troubleshoot.md b/articles/application-gateway/ingress-controller-troubleshoot.md index 89e4433219a17..4391fbfaca4e6 100644 --- a/articles/application-gateway/ingress-controller-troubleshoot.md +++ b/articles/application-gateway/ingress-controller-troubleshoot.md @@ -316,4 +316,4 @@ aksClusterConfiguration: ## Review Application Gateway Activity Log -> When troubleshooting Application Gateway Ingress Controller issues, it's good practice to check the Application Gateway's Activity Log in addition to kubernetes resources. Every time AGIC applies a new configuration, a corresponding entry is recorded in the Activity Log in the Azure portal. Reviewing these entries helps to confirm whether configuration updates were successfully applied and can often reveals gateway-related issues that aren't visible from the kubernetes side. +> When troubleshooting Application Gateway Ingress Controller issues, it's good practice to check the Application Gateway's Activity Log in addition to Kubernetes resources. Every time AGIC applies a new configuration, a corresponding entry is recorded in the Activity Log in the Azure portal. Reviewing these entries helps to confirm whether configuration updates were successfully applied and can often reveal gateway-related issues that aren't visible from the Kubernetes side.