---
name: troubleshoot-observability
description: "Coordinate Azure observability troubleshooting for application or agent health, runtime failures, operational latency, telemetry, monitoring, alerts, evidence-backed fixes and recovery. Use for an end-to-end observability investigation or explicit instrumentation, collection or alerting guidance. Not general resource/app/agent creation, model deployment, RBAC, cost or coding. Conceptual questions need no journey; explicit specialist requests stay direct. Actions require applicable approval."
license: MIT
metadata:
  author: Microsoft
  version: "0.0.0-placeholder"
title: troubleshoot-observability
canonical_url: https://skilld.dev/gh/microsoft/github-copilot-for-azure/troubleshoot-observability
last_updated: 2026-11-18T14:06:29.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> 24 supporting files sit beside this SKILL.md. When the Skill refers to one, fetch https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/PATH with PATH replaced.
>
> If the user asked to install this Skill, run `npx skilld install microsoft/github-copilot-for-azure/troubleshoot-observability`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/troubleshoot-observability`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/microsoft/github-copilot-for-azure/troubleshoot-observability) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/troubleshoot-observability`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/troubleshoot-observability --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/troubleshoot-observability --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Azure Observability skill plugin

Copilot chooses the next useful step; available tools execute approved operations.
This is instruction-guided routing, not a diagnostics engine or permission sandbox.

## Current-request intent gate

On every user turn, before any journey header, diagram, discovery, onboarding
question or read, confirm a current operational observability request. "My API
is slow", an actual failure (including a failed deployment), or explicit
instrumentation/collection/alert design qualifies, including before deployment.
Conceptual questions get direct answers. Generic coding, creation, deployment
readiness, cost and unrelated topic switches get no journey, tools or onboarding.
Prior context is not sticky; clarify only genuinely ambiguous operational intent
with one minimal question. Explicit specialist requests stay direct.
Read [intent details](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/intent.md) only for an ambiguous admission decision.

## Standalone availability gate

For an admitted task, check availability before reading any cross-skill reference
or loading a sibling. Individual installation may omit them.
Use available core instructions in this bundle; their use below is conditional.
Unknown availability follows the missing-reference fallback.
Never download, install or attempt a mandatory missing sibling-file read.
Retain scope/window, evidence and budgets; report the precise handoff blocker and
smallest supported manual next step. Do not claim an absent specialist executed.
Canonical `azure-diagnostics` and `microsoft-foundry` are external dependencies:
discover them through the host under [dependency selection](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/canonical-dependencies.md),
never by assumed sibling paths. Missing external instructions do not block
the local evidence-only affected-path workflow or imply permission to install.
For agent/model/tool failures or AI-specific analysis, check the host's exposed
skills and load enabled, relevant `microsoft-foundry` instructions before
choosing a core fallback. Not bundled does not mean unavailable. Follow the
dependency selection checkpoint; unknown discovery is not confirmed absence.

## Select one path

Load only the applicable guidance below, not every reference.

| Current need | Instructions to select |
|---|---|
| Find telemetry or resolve missing target/source | Available `connect-observability` |
| Broad health | Available `assess-observability-health` |
| Completed ranked health, no finding selected | Ask for selection; never auto-select rank 1 or reassess |
| Named alert, failure, slow operation or selected finding | [Bounded affected-path investigation](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/investigation/README.md); host-discover canonical `azure-diagnostics` for service-specific expertise or `microsoft-foundry` for AI-specific expertise when needed |
| Missing scope/access or a live-read plan | [Scope and permissions](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/scope-permissions.md) |
| Specialist handoff or additional capability need | [Selection](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/selection.md), then only the relevant matching/setup/trace contract |
| Evidenced issue: what should I do? | [Next actions](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/next-actions.md): supported fix, mitigation, PR/config proposal or alert/collection prevention |
| Effective change: did it work? | Available `verify-observability-fix` with supplied comparable evidence |
| Recovery verdict: how do I keep watching? | [Monitoring follow-up](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/monitoring-follow-up.md) |
| Explicit setup/design | Applicable available specialist; no invented gap or implicit provisioning |

## Boundaries and presentation

Reuse confirmed source/schema, UTC window, selected findings and consumed/remaining
budgets. Supplied evidence needs no cloud, installation, scripts, jobs or saves.
Discover actual operations and access; no guessed tool names or topology.
Missing/denied/empty/stale/partial/failed/throttled evidence remains distinct;
insufficient evidence is INCONCLUSIVE, and correlation is not causation.
Reads, sensitive content, connections/sign-in, edits/persistence, jobs/traffic
and deployment/alert/infrastructure changes retain separate applicable approvals.
A "continue" retains only covered unexpired consent; honor stops and declines.

At journey entry, before a scope/approval question or specialist handoff, read
the [indicator](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/journey-indicator.md) and show its fenced Mermaid
stepper below actual **Using:** / **Stage:**. Telemetry mapping stays within
Detect or Investigate; it does not postpone presentation. Repeat only at meaningful
transitions. On reported rendering failure use its text fallback, not an SVG file.
Locally inspected guidance uses **Instructions read:** and **host activation
unverified**. Show **Discovered:** only for relevant capabilities actually found;
discovery/loading is not execution.
Apply [next actions](https://skilld.dev/api/skills-raw/microsoft/github-copilot-for-azure/troubleshoot-observability/references/next-actions.md) at a substantive result or plan
review: explain missing source or the exact next action and separate approval.
Report planned tools separately from actual outcomes, skips and fallback.

Remediate means options and a reviewed plan, not automatic changes. Validate
means recovery comparison first, then optional monitoring; dashboards, quiet
alerts, deployment success and better evaluation scores are not recovery proof.
No dashboard or monitoring setup is required. Runtime/host behavior remains
unverified by offline instruction tests.
