aspire-diagnostics

Diagnose running Aspire apps using resource state, logs, traces, and metrics.

2.5k|507|Updated Feb 7, 2014
One-click install
npx skills add https://github.com/exceptionless/Exceptionless --skill aspire-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-diagnostics
Source: https://github.com/exceptionless/Exceptionless/tree/main/.agents/skills/aspire-diagnostics
Command: npx skills add https://github.com/exceptionless/Exceptionless --skill aspire-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a locally running Exceptionless Aspire app misbehaves, guessing at the cause wastes time. This Skill provides a structured workflow for gathering runtime evidence—resource state, structured logs, OpenTelemetry traces, spans, metrics, and browser telemetry—before deciding whether code changes are needed.

Core Features & Use Cases

  • Resource and Log Inspection: Check resource state with aspire describe, then pull structured OpenTelemetry logs and console logs per resource.
  • Trace and Span Analysis: Follow cross-resource failures or latency by retrieving traces and drilling into spans by trace ID.
  • Performance Measurement: Count API, Redis, Elasticsearch, queue, and job calls produced by a single user action and identify the slowest spans.
  • Use Case: A frontend page loads slowly in the local Svelte app. You perform the action once, pull recent traces, inspect spans for the trace, and discover repeated Elasticsearch queries causing the delay.

Quick Start

Ask the AI to investigate why a local request is failing by checking Aspire resource state, structured logs, and traces for the affected resource.

Frequently Asked Questions about aspire-diagnostics

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

FAQPage Schema
How do I check logs for a running Aspire app?

Use `aspire otel logs <resource> --limit 100 --format Json --non-interactive` for structured OpenTelemetry logs, or `aspire logs <resource> --tail 100 --timestamps` for console process output. Check resource state first with `aspire describe` to get exact resource names.

How to trace a slow request across Aspire resources?

Pull recent traces with `aspire otel traces --limit 50 --format Json`, identify the trace matching your user action, then inspect its spans with `aspire otel spans --trace-id <traceId>`. Count calls by dependency to find repeated or slow operations.

Can Aspire diagnostics capture browser console logs?

Yes, when the AppHost enables `WithBrowserLogs()` on frontend resources, the Aspire dashboard surfaces browser console logs, network requests, and screenshots. This helps explain frontend failures without separate browser tooling.

When should I not use Aspire diagnostics?

Do not use it for ordinary code reading, narrow edits, or normal build and test work. It is meant for investigating unclear runtime behavior where logs, traces, or resource state evidence is needed before changing code.

Does Aspire diagnostics work for deployed production environments?

No, the local Aspire CLI workflow assumes a locally running AppHost. For deployed or external environments, get explicit user scope and use the hosting platform's own diagnostics and monitoring tools instead.