Skip to content

Add note about importance of checking Application Gateway Activity Logs #127775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+5 −0
Open

Add note about importance of checking Application Gateway Activity Logs #127775

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
897a9f0
add note about importance of checking Application Gateway Activity Logs
rishisingh0722 Oct 24, 2025
b2cb104
Fix typos in troubleshooting guide
rishisingh0722 Oct 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions articles/application-gateway/ingress-controller-troubleshoot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -312,3 +312,8 @@ rbac:
aksClusterConfiguration:
apiServerAddress: <aks-api-server-address>
```


## 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 reveal gateway-related issues that aren't visible from the Kubernetes side.