aspire-monitoring

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

Updated Jan 20, 2021
One-click install
npx skills add https://github.com/Stavanger-Brass-Band/sheetmusic-api --skill aspire-monitoring-stavanger-brass-band
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire-monitoring
Source: https://github.com/Stavanger-Brass-Band/sheetmusic-api/tree/main/.agents/skills/aspire-monitoring
Command: npx skills add https://github.com/Stavanger-Brass-Band/sheetmusic-api --skill aspire-monitoring-stavanger-brass-band

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Diagnosing issues in distributed .NET Aspire applications requires knowing which observability tool applies to each environment, and this Skill routes monitoring requests to the correct CLI commands for local, AKS, Azure, and Docker deployments. ## Core Features & Use Cases - Local Telemetry Inspection: Retrieve console logs, structured OpenTelemetry logs, distributed traces, and spans using aspire logs and aspire otel commands against a running AppHost. - Environment-Based Routing: Direct diagnostics to kubectl and Container Insights for AKS workloads, azure-diagnostics for deployed Azure resources, or Docker CLI for Compose deployments. - Standalone Dashboard Support: Launch the Aspire Dashboard without an AppHost and query it remotely using --dashboard-url and --api-key flags. - Use Case: When an API resource appears unhealthy, run aspire describe to check resource state, then aspire otel logs to find structured errors, and aspire otel traces to follow the failing request across services. ## Quick Start Ask the agent to show the structured logs and current resource state of the running Aspire app to diagnose why a service is failing.

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 a running Aspire application?▼

Use aspire logs <resource> for console stdout/stderr output, or aspire otel logs for structured OpenTelemetry log records. Add --follow to stream logs in real time and --format Json for machine-readable output.

How do I see distributed traces in .NET Aspire?▼

Run aspire otel traces to view distributed trace data and aspire otel spans for individual span detail. You can correlate logs to a specific request using aspire otel logs --trace-id <id>.

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

No, the Aspire CLI communicates through a local backchannel socket and cannot reach remote AppHosts. For AKS use kubectl and Container Insights, for other Azure targets use azure-diagnostics, unless a reachable dashboard allows aspire otel queries via --dashboard-url.

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

Resources marked hidden in the AppHost, such as proxies, helper containers, and migrations, are filtered by default. Re-run the command with the --include-hidden flag to see the full resource list.

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. The command is foreground and blocking, so agents must launch it as a background process and capture the login URL and token.