AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-diagnostics

Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-diagnostics at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 42

troubleshooting/aks/references/structured-input-modes.md

AKS Structured Input Modes

Use this reference when the troubleshooting request already contains structured inputs.

Detector-backed Mode

Use when AKS-aware detectors or AppLens-style insights are available.

Decision rules:

  • Ignore findings where the detector is emergingIssues.
  • Prefer critical findings over warnings.
  • Prefer findings with more concrete remediation detail when choosing the likely root problem.
  • Preserve per-insight output: problem summary, root-problem flag, affected resources, suggested commands.

Warning Events Mode

Use when the request includes Kubernetes warning events.

Expected output:

  • summary of the events and their impact
  • likely cause or causes
  • next kubectl checks
  • monitoring follow-up

Metrics Scan Mode

Use when the request includes CPU or memory time-series data.

Expected output:

  • healthy or unhealthy status
  • anomaly timestamps and explanations
  • suggestion tied to the observed metric pressure

Generic Symptoms Mode

Use when the request includes resource symptoms but not detector results, warning events, or time-series metrics.

Expected output:

  • symptom summary by resource
  • likely failure domain
  • next evidence-collection steps

Learn Grounding Fallback

If the first troubleshooting pass is incomplete, search Microsoft Learn using:

  • the user prompt
  • the parsed problem names
  • the AKS troubleshooting context

Use Learn grounding to refine or validate the root-cause hypothesis, not to replace observed evidence.