aspire-monitoring
**ANALYSIS SKILL** - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard. Routes between local Aspire CLI, AKS workload diagnostics, and deployed Azure resource health. USE FOR: aspire logs, aspire otel logs, aspire otel traces, aspire otel spans, aspire describe, aspire ps, aspire export, aspire dashboard run, --include-hidden, browser logs in dashboard, WithBrowserLogs, App Insights query, AKS pod logs, container app logs. DO NOT USE FOR: start/stop/wait (use aspire-orchestration), deploy/publish/destroy (use aspire-de
Profile →npx skills add microsoft/aspire-skills --skill aspire-monitoring --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Aspire Monitoring > Aspire CLI provides full observability **locally**. For deployed apps, route to platform-specific tools. ## Diagnostics Bridge — Where To Look | Need | Environment | Tool | Command / Route | |------|------------|------|-----------------| | Console logs | Local dev | Aspire CLI | `aspire logs <resource>` | | Structured logs | Local dev | Aspire CLI | `aspire otel logs [resource]` | | Distributed traces | Local dev | Aspire CLI | `aspire otel traces [resource]` | | Span detail | Local dev | Aspire CLI | `aspire otel spans [resource]` | | Resource state | Local dev | Aspire CLI | `aspire describe` (add `--include-hidden` if a resource is missing) | | Telemetry export | Local dev | Aspire CLI | `aspire export [resource]` | | Standalone dashboard | Any (no AppHost) | Aspire CLI | `aspire dashboard run` (foreground/blocking — see below) | | Browser console / network / screenshots | Local dev (frontend) | Aspire dashboard | Surfaced via `Aspire.Hosting.Browsers` + `WithBrowserLogs()` | | AppHost / deployment definition | Authoring | aspire-deployment skill | → `aspire-deployment` skill | | AKS workload (pod logs, pod state) | Deployed AKS | kubectl + Container Insigh
- Diagnostics Bridge — Where To Look
- Investigation Workflow
- Local Commands Reference
- Hidden resources are filtered by default
- Tips for Agents
- Known Diagnostics Issues
- Standalone Dashboard (aspire dashboard run)
- Connect the Aspire CLI to a standalone dashboard
- Browser Telemetry (Aspire.Hosting.Browsers)
- Dashboard UX Features
- Why Aspire CLI Can't Do Remote Diagnostics
- Handoff Rules
- Project-Local Skill Routing
- References
aspire describe --format Json
aspire ps --include-hidden --format Json | jq '.[] | {name, displayName, state, hidden}'
aspire describe --apphost ./src/MyApp.AppHost/
aspire dashboard run
Stream structured logs from a standalone dashboard (login URL form)
aspire otel logs --dashboard-url "http://localhost:18888/login?t=TOKEN" --follow
Search recent traces
aspire otel traces --dashboard-url "http://localhost:18888/login?t=TOKEN"
aspire otel logs --dashboard-url https://my-dashboard.example.com --api-key "$DASHBOARD_API_KEY" --followWhat does the aspire-monitoring skill do?
**ANALYSIS SKILL** - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard. Routes between local Aspire CLI, AKS workload diagnostics, and deployed Azure resource health. USE FOR: aspire logs, aspire otel logs, aspire otel traces, aspire otel spans, aspire describe, aspire ps, aspire export, aspire dashboard run, --include-hidden, browser logs in dashboard, WithBrowserLogs, App Insights query, AKS pod logs, container app logs. DO NOT USE FOR: start/stop/wait (use aspire-orchestration), deploy/publish/destroy (use aspire-de
How do I install it?
Run `npx skills add microsoft/aspire-skills --skill aspire-monitoring --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From microsoft/aspire-skills, a repository with 76 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.