aspire-monitoring

To diagnose an unhealthy Aspire application resource, you inspect structured logs, distributed traces, metrics, and resource states. This skill correlates telemetry data and applies environment-aware diagnostic routing using Aspire CLI, Azure diagnostics, kubectl, or Docker tooling based on the deployment target.

The best way to view Aspire traces and metrics during local development is using Aspire diagnostics tooling and CLI workflows. This skill routes local telemetry inspection through the correct standalone dashboard or CLI commands to locate spans and structured logs.

Yes, Aspire monitoring supports Azure deployments and AKS workloads. The skill uses environment-aware diagnostic routing to determine whether to inspect telemetry using Azure diagnostics, kubectl, or Docker tooling based on where the application is running.

To export Aspire diagnostics for a failing service, you inspect browser diagnostics, correlate telemetry, and prepare sharable diagnostic exports. The skill identifies resource health and routes the export workflow through the appropriate environment-specific diagnostic tool.

You need OpenTelemetry inspection for Aspire apps when investigating running applications to locate exported telemetry, distributed traces, and spans. This process helps correlate structured logs and resource states to troubleshoot failing services across local or containerized environments.