aspire-monitoring

Inspects Aspire app logs, traces, metrics, and resource state via the Aspire CLI.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill aspire-monitoring-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-monitoring
Source: https://github.com/codebytes/btt/tree/main/.agents/skills/aspire-monitoring
Command: npx skills add https://github.com/codebytes/btt --skill aspire-monitoring-codebytes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Diagnosing issues in distributed Aspire applications requires knowing which observability tool to use for each environment, and this Skill routes every monitoring question to the correct command for local, AKS, Azure, or Docker deployments. ## Core Features & Use Cases - Local Telemetry Inspection: Query console logs, structured OpenTelemetry logs, distributed traces, and spans with commands like aspire logs, aspire otel logs, and aspire otel traces. - Resource State Discovery: Use aspire describe and aspire ps with --include-hidden and --format Json to find endpoints, health status, and hidden resources. - Deployed App Routing: Direct diagnostics for AKS workloads to kubectl and Container Insights, Azure resources to azure-diagnostics, and Docker targets to docker logs. - Use Case: When an API resource fails locally, run aspire describe to check state, then aspire otel logs <resource> for structured errors, and aspire otel traces to follow the failing request across services. ## Quick Start Ask the agent to check why a resource is failing by running aspire describe and aspire otel logs for that resource.

Frequently Asked Questions about aspire-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view logs for an Aspire resource?

Run `aspire logs <resource>` for console output or `aspire otel logs <resource>` for structured OpenTelemetry logs. Add `--follow` to stream in real time, or use `--search` to filter by text across messages and attributes.

How do I see distributed traces in an Aspire app?

Use `aspire otel traces [resource]` to view distributed trace data and `aspire otel spans [resource]` for span-level detail. You can correlate logs to a trace with `aspire otel logs --trace-id <id>`.

Why is a resource missing from aspire ps or aspire describe?

The Aspire CLI filters out hidden resources such as proxies, helper containers, and migrations by default. Re-run the command with `--include-hidden` to see the full resource list.

Can the Aspire CLI diagnose apps deployed to Azure or AKS?

No, the Aspire CLI uses a local backchannel socket and cannot reach remote AppHosts. For AKS use kubectl and Container Insights, for other Azure resources use azure-diagnostics, and for Docker use docker logs.

How do I run the Aspire dashboard without an AppHost?

Run `aspire dashboard run`, which starts a standalone dashboard accepting OTLP telemetry on ports 4317 and 4318. It is a blocking foreground process, so agents must launch it as a background task and capture the login URL with its token.

How do I query telemetry from a standalone Aspire dashboard?

Pass the dashboard login URL to `aspire otel logs --dashboard-url` or `aspire otel traces --dashboard-url`; the CLI normalizes the token automatically. For API-key-authenticated dashboards, add `--api-key` alongside the base URL.