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.