[Question] How to diagnose Backend health issues with Azure Application Gateway for Containers
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 395
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 13
Description
**Describe scenario**
Hello, we are using Azure Application Gateway for Containers in two AKS clusters. In one of them, we have suddenly started seeing issues with the backend target health probes. Pretty much all endpoints are shown as UNHEALTHY most of the time when accessing the backend Health endpoint of the master ALB controller Pod (http://:8000/backendHealth). But even with details, what is missing is some information of what actually went wrong so that it became UNHEALTHY.
In the legacy Application Gateway there was actually a page where you could see which backend health check was invoked and what went wrong (i.e. https://learn.microsoft.com/en-us/troubleshoot/azure/application-gateway/application-gateway-backend-health-troubleshooting#backend-health-status-unhealthy)
**Question**
How to troubleshoot backend health issues in Application Gateway for Containers?
Contributor guide
Assessment
This issue has not been assessed yet.