OpenParable
Skip to content
← Back to skills

Application Gateway Troubleshooting

DevOps & Security
application-gateway-troubleshooting

Application Gateway Troubleshooting is an Agent Skill for devops & security published in the HolmesGPT/holmesgpt repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Troubleshooting Application Gateway Problems

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/HolmesGPT/holmesgpt/blob/HEAD/tests/llm/fixtures/test_ask_holmes/90_skill_basic_selection/application-gateway-troubleshooting/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/application-gateway-troubleshooting, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Application Gateway Troubleshooting

Overview

This runbook helps troubleshoot common Application Gateway issues including 502 Bad Gateway errors.

Prerequisites

  • kubectl access to the cluster
  • Ability to view pod logs

Troubleshooting Steps

Step 1: Find the Application Gateway Pod Status

Use kubectl to check if the Application Gateway pod is running:

kubectl get pods -n <namespace> | grep application-gateway

Step 2: Check Application Gateway error Logs

Review the Application Gateway error logs for any issues:

kubectl logs <application-gateway-pod> -n <namespace> --tail=100 | grep -i error

Step 3: Verify Upstream Services

Check if the upstream services that Application Gateway proxies to are healthy:

kubectl get pods -n <application-gateway-pod> -l app=upstream-service

Step 4: Check Application Gateway Configuration

Verify the Application Gateway configuration is valid:

kubectl exec <application-gateway-pod> -n <namespace> -- appg -t

Step 5: Review Service Endpoints

Ensure the Application Gateway has healthy endpoints:

kubectl get endpoints -n <namespace>

Resolution Steps

Based on findings:

  • If upstream is down: Restart upstream services
  • If config invalid: Fix configuration and reload
  • If no endpoints: Check service selectors