startup-perf

Capture Aspire startup OTEL traces and export a dashboard trace archive.

6.2k|952|Updated Sep 25, 2023
One-click install
npx skills add https://github.com/microsoft/aspire --skill startup-perf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: startup-perf
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/startup-perf
Command: npx skills add https://github.com/microsoft/aspire --skill startup-perf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing where time is spent when Aspire applications start, making regressions hard to detect and performance investigations slow.

Core Features & Use Cases

  • Captures end-to-end startup traces: Uses Aspire’s hidden CLI self-profile flow to collect OTEL traces from the CLI, the AppHost hosting layer, and (when applicable) DCP startup telemetry.
  • Exports a reusable trace artifact: Produces a zip containing an OTLP JSON trace export you can inspect and compare before/after changes.
  • Separates profiling from reported telemetry: Ensures profiling spans and high-cardinality profiling identifiers do not contaminate production telemetry by design.
  • Use cases: Investigate startup slowdowns, validate performance-impacting changes in AppHost code, and compare baseline vs. feature branch startup behavior with correlated spans.

Quick Start

Run an Aspire command with the hidden capture flag and write the exported trace zip to artifacts/tmp/startup-profile/profile.zip so you can inspect trances in profile.json after startup completes.

Frequently Asked Questions about startup-perf

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

FAQPage Schema
How do I trace Aspire startup performance to find bottlenecks?

You trace Aspire startup performance by running the AppHost with a hidden CLI capture flag to collect OTEL traces, exporting a zip archive containing the OTLP JSON profile for inspection.

What is the best way to profile an Aspire AppHost startup slowdown?

Profiling an Aspire AppHost startup slowdown is best done by capturing distributed OTEL traces across the CLI, hosting layer, and DCP, isolating profiling spans from production telemetry to identify exact time expenditures.

Does Aspire's startup profiling separate trace data from regular telemetry?

Aspire's startup profiling separates trace data from regular telemetry by using profiling-specific ActivitySources and session scoping, preventing high-cardinality profiling identifiers from contaminating production reporting.

Can I compare baseline and feature branch startup traces for Aspire applications?

You can compare baseline and feature branch startup traces for Aspire applications by generating reusable OTLP JSON trace zip exports before and after changes, then inspecting correlated spans to validate performance impacts.

How do I export an OTLP JSON trace file for Aspire startup profiling?

You export an OTLP JSON trace file for Aspire startup profiling by utilizing the CLI self-profile flow, which writes a dashboard trace archive zip to a specified artifacts directory containing a profile.json file.