Menu
Troubleshooting Application Gateway Problems
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/HolmesGPT/holmesgpt --skill application-gateway-troubleshootingThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | application-gateway-troubleshooting |
| description | Troubleshooting Application Gateway Problems |
This runbook helps troubleshoot common Application Gateway issues including 502 Bad Gateway errors.
Use kubectl to check if the Application Gateway pod is running:
kubectl get pods -n <namespace> | grep application-gateway
Review the Application Gateway error logs for any issues:
kubectl logs <application-gateway-pod> -n <namespace> --tail=100 | grep -i error
Check if the upstream services that Application Gateway proxies to are healthy:
kubectl get pods -n <application-gateway-pod> -l app=upstream-service
Verify the Application Gateway configuration is valid:
kubectl exec <application-gateway-pod> -n <namespace> -- appg -t
Ensure the Application Gateway has healthy endpoints:
kubectl get endpoints -n <namespace>
Based on findings:
Any Elasticsearch error-log query against app-279-logs-* — these indices use ``lvl`` (keyword) for log severity, not ``severity`` or ``level``.
Guide for investigating slow PostgreSQL queries
AWS Lambda High Latency Troubleshooting
Based on SOC occupation classification
