Skip to content

Conversation

@rishisingh0722
Copy link

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.
https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-troubleshoot

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.
@prmerger-automator
Copy link
Contributor

@rishisingh0722 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 897a9f0:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/ingress-controller-troubleshoot.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards requested a review from Copilot October 24, 2025 15:05
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a troubleshooting reminder to check Application Gateway Activity Logs when debugging AGIC (Application Gateway Ingress Controller) issues. This helps users verify configuration updates and detect gateway-related problems that may not be visible from the Kubernetes side.

Key Changes:

  • Added new section "Review Application Gateway Activity Log" with guidance on checking Activity Logs for AGIC configuration updates

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@v-dirichards
Copy link
Contributor

@mbender-ms

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Oct 24, 2025
Corrected capitalization of 'Kubernetes' and fixed 'reveals' to 'reveal'.
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit b2cb104:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/ingress-controller-troubleshoot.md ✅Succeeded

For more details, please refer to the build report.

@rishisingh0722 rishisingh0722 changed the title add note about importance of checking Application Gateway Activity Logs Add note about importance of checking Application Gateway Activity Logs Oct 27, 2025
@prmerger-automator
Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @mbender-ms

1 similar comment
@prmerger-automator
Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @mbender-ms

@v-dirichards
Copy link
Contributor

@mbender-ms - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants