Gap-6: App Service Diagnose (B → A) — Dedicated troubleshooting guide + MCP tool usage

[paulyuk]

Parent: #1608

App Service Diagnose: B → A

Learning from: Container Apps (B+) — dedicated troubleshooting guide with specific flows for image pulls, cold starts, health probes

Current state: No dedicated App Service diagnostic reference. Falls back to general AppLens. Despite having 7 MCP commands, no guidance on when/how to use each.

Deliverables

• references/app-service/README.md in azure-diagnostics — Troubleshooting guide:
  • High CPU/memory diagnosis (specific AppLens detectors)
  • Deployment failure analysis (Kudu logs, deployment history API)
  • Application crash/restart diagnosis (Event Log, STDERR)
  • Slow response time investigation (request tracing, dependency analysis)
  • Custom domain / TLS certificate issues
• MCP tool usage guide — when to use each of the 7 App Service MCP commands for diagnostics
• Add 2 integration tests: deployment failure troubleshooting, high CPU diagnosis

Key Scenarios

• "My app is slow" → CPU profiler, request traces, dependency map
• "My deployment failed" → Kudu logs, SCM site, deployment history
• "My app keeps restarting" → event logs, health check failures, memory limits

⚠️ Starting assessment — domain experts should modify or contribute what they believe is essential.

[github-actions]

Thanks for opening this issue, @paulyuk! 🙌

This has been labeled azure-diagnostics and enhancement since it tracks the addition of a dedicated App Service troubleshooting reference guide and MCP tool usage guidance within the diagnostics skill. The integration-test label was also added given the explicit ask for two new integration tests covering deployment failure and high CPU diagnosis scenarios. The untriaged label has been removed now that the issue is categorized.

This looks like well-scoped, actionable work — the deliverables are clearly defined and ready to be picked up!

Generated by Issue Triage for issue #1614 · ◷