aspire-monitoring

Diagnose Aspire application observability issues by inspecting logs, traces, metrics, and resource states.

Updated Jul 14, 2026

Search Tags:#monitoring #logs #diagnostics #telemetry #opentelemetry #traces #aspire

Ready to run

npx skills add https://github.com/ojrojas/OroIdentityServer --skill aspire-monitoring-ojrojas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire-monitoring
Source: https://github.com/ojrojas/OroIdentityServer/tree/main/.agents/skills/aspire-monitoring
Command: npx skills add https://github.com/ojrojas/OroIdentityServer --skill aspire-monitoring-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers investigate running Aspire applications by locating logs, traces, metrics, resource states, and telemetry through the correct diagnostics workflow.

Core Features & Use Cases

Aspire Observability: Inspect local application resources, structured logs, distributed traces, spans, and exported telemetry using Aspire diagnostics tooling.
Environment-Aware Routing: Determine whether to use Aspire CLI, Azure diagnostics, kubectl, or Docker tooling based on where the application is running.
Use Case: When an Aspire service is failing, use this Skill to identify resource health, correlate telemetry, inspect browser diagnostics, and prepare sharable diagnostic exports.

Quick Start

Use the aspire-monitoring skill to investigate why my Aspire application resource is unhealthy and identify the relevant logs and traces.

Frequently Asked Questions about aspire-monitoring

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

FAQPage Schema

How do I diagnose an unhealthy Aspire application resource?▼

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.

What's the best way to view Aspire traces and metrics during local development?▼

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.

Does Aspire monitoring work with Azure deployments and AKS workloads?▼

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.

How do I export Aspire diagnostics for a failing service?▼

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.

When do I need OpenTelemetry inspection for Aspire apps?▼

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.