What problem does it solve? Diagnosing issues in distributed Aspire applications requires knowing where telemetry lives—locally via the Aspire CLI, in a standalone dashboard, or in deployed environments like AKS and Azure Container Apps. This Skill routes observability requests to the correct tool and provides the exact commands for each scenario. ## Core Features & Use Cases - Local Telemetry Inspection: Query console logs, structured OpenTelemetry logs, distributed traces, and spans with aspire logs, aspire otel logs, aspire otel traces, and aspire otel spans. - Resource State Discovery: Use aspire describe and aspire ps (with --include-hidden for proxies and helper containers) to find endpoints and health status. - Diagnostics Routing: Decision tree routes deployed-app diagnostics to kubectl, azure-diagnostics, or Docker CLI based on the hosting target. - Standalone Dashboard: Launch aspire dashboard run as a background process and query it remotely via --dashboard-url and --api-key. - Use Case: When an API resource returns errors, run aspire otel logs apiservice --search "error" to find structured log entries, then correlate with aspire otel traces to identify the failing dependency. ## Quick Start Ask the assistant to show the structured logs and current resource state of your running Aspire app.
