aspire-monitoring

Collect and diagnose Aspire app health from logs, traces, metrics, and browser telemetry.

13|4|Updated Feb 8, 2025
One-click install
npx skills add https://github.com/jonathanpotts/aspire-nextjs-keycloak --skill aspire-monitoring-jonathanpotts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-monitoring
Source: https://github.com/jonathanpotts/aspire-nextjs-keycloak/tree/main/.agents/skills/aspire-monitoring
Command: npx skills add https://github.com/jonathanpotts/aspire-nextjs-keycloak --skill aspire-monitoring-jonathanpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Aspire-powered applications often produce rich telemetry (logs, traces, metrics) but organizations struggle to surface, correlate, and act on it across local development, AppHost dashboards, and deployed environments. This skill consolidates guidance and workflows to observe and diagnose Aspire apps end-to-end, from browser telemetry to container metrics, with clear routing between local Aspire CLI workflows and platform-specific diagnostics.

Core Features & Use Cases

  • Collect and correlate console logs, structured telemetry, and browser telemetry from frontends and backends.
  • Route diagnostics to the appropriate toolchains (Aspire CLI for local development, kubectl + Container Insights for AKS, and azure-diagnostics for Azure resources).
  • Provide a unified workflow for investigative tasks, telemetry export, and dashboard-based observability.

Quick Start

Observe your Aspire app locally and surface telemetry via the dashboard with guided steps.

Frequently Asked Questions about aspire-monitoring

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

FAQPage Schema
How do I collect and view telemetry from my Aspire app?

You collect Aspire telemetry by using the Aspire CLI and Standalone Dashboard to surface logs, traces, metrics, and browser telemetry without code changes, providing unified observability across local and deployed environments.

How do I diagnose Aspire app health issues in AKS?

Diagnose Aspire app health in AKS by using kubectl commands and Container Insights to collect container metrics and traces, routing platform-specific diagnostics to surface performance signals for your deployed workloads.

What is the best way to monitor Azure resources deployed by Aspire?

Monitor deployed Azure resources by routing diagnostics through Azure Monitor to collect and correlate telemetry, surfacing health and performance signals across your deployed Aspire application infrastructure.

Does Aspire observability work without modifying my application code?

Yes, Aspire observability requires no code changes, leveraging Aspire CLI commands, kubectl for AKS, and Azure Monitor to collect logs, traces, metrics, and browser telemetry end-to-end.

Can I correlate frontend browser telemetry with backend logs in Aspire?

Yes, you can collect and correlate console logs, structured telemetry, and browser telemetry from both frontends and backends to provide a unified workflow for investigative tasks and dashboard-based observability.

When should I use the Standalone Dashboard for Aspire monitoring?

Use the Standalone Dashboard for remote telemetry collection to observe Aspire app health, surface performance signals, and investigate issues when working outside the local AppHost environment.