poc: aspire telemetry cli

[Hona]

adds a WHOLE bunch of commands to be able to get all the OTEL data you could want via the CLI/MCP...

example usage:

🔥 Cool Demo Commands
Traces
# List recent traces (newest first)
aspire telemetry traces --dashboard-url https://localhost:18888
# Get specific trace by ID
aspire telemetry traces abc123def456 --dashboard-url https://localhost:18888
# Filter traces with errors only
aspire telemetry traces --filter "status=Error" --dashboard-url https://localhost:18888
# Search span names
aspire telemetry traces --search "api/orders" --dashboard-url https://localhost:18888
# Filter by resource and HTTP method
aspire telemetry traces --resource apiservice --filter "http.method=POST" --dashboard-url https://localhost:18888
# JSON output for piping to jq
aspire telemetry traces --json --limit 5 --dashboard-url https://localhost:18888 | jq '.traces[0]'
Logs
# List recent logs
aspire telemetry logs --dashboard-url https://localhost:18888
# Filter by severity (Warning and above)
aspire telemetry logs --severity Warning --dashboard-url https://localhost:18888
# Errors only
aspire telemetry logs --severity Error --dashboard-url https://localhost:18888
# Filter by resource
aspire telemetry logs --resource basket --dashboard-url https://localhost:18888
# Logs for a specific trace
aspire telemetry logs --trace abc123def456 --dashboard-url https://localhost:18888
# Message contains filter
aspire telemetry logs --filter "message~connection refused" --dashboard-url https://localhost:18888
Metrics
# List all metrics for a resource
aspire telemetry metrics --resource apiservice --dashboard-url https://localhost:18888
# Get specific metric data (meter/instrument format)
aspire telemetry metrics "System.Net.Http/http.client.request.duration" --resource apiservice --dashboard-url https://localhost:18888
# Custom time duration
aspire telemetry metrics "System.Net.Http/http.client.request.duration" --resource apiservice --duration 30m --dashboard-url https://localhost:18888
Fields Discovery
# List all available telemetry fields
aspire telemetry fields --dashboard-url https://localhost:18888
# List only trace fields
aspire telemetry fields --type traces --dashboard-url https://localhost:18888
# Get values for a specific field (great for building filters!)
aspire telemetry fields http.method --dashboard-url https://localhost:18888
# Get log categories
aspire telemetry fields category --type logs --dashboard-url https://localhost:18888
Combining Filters (Power User)
# Multiple filters (AND logic)
aspire telemetry traces \
  --resource apiservice \
  --filter "http.method=POST" \
  --filter "http.response.status_code>=400" \
  --dashboard-url https://localhost:18888
# Complex log query
aspire telemetry logs \
  --resource basket \
  --severity Warning \
  --filter "category~Microsoft.EntityFrameworkCore" \
  --limit 50 \
  --json \
  --dashboard-url https://localhost:18888
Help Commands (show polish)
aspire telemetry --help
aspire telemetry traces --help
aspire telemetry logs --help

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 13727

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 13727"

[Copilot]

Pull request overview

This PR introduces a proof-of-concept CLI interface for querying telemetry data (traces, logs, metrics) from the Aspire Dashboard via the Model Context Protocol (MCP). The implementation adds filtering capabilities, field discovery tools, and human-readable formatting for CLI output.

Key changes:

• New MCP tools for querying metrics and discovering available telemetry fields
• Enhanced trace and log filtering with JSON-based filter expressions
• CLI output formatter with support for traces, logs, metrics, and field data
• Comprehensive test coverage for new functionality

Reviewed changes

Copilot reviewed 76 out of 78 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tests/Aspire.Dashboard.Tests/Mcp/AspireTelemetryMcpToolsTests.cs	Adds tests for filtering traces/logs and the new get_trace tool
tests/Aspire.Dashboard.Tests/Mcp/AspireMetricsMcpToolsTests.cs	New test file for metrics MCP tools functionality
tests/Aspire.Dashboard.Tests/Mcp/AspireFieldsMcpToolsTests.cs	New test file for telemetry fields discovery tools
tests/Aspire.Dashboard.Tests/Integration/McpServiceTests.cs	Updates integration tests to verify new MCP tools are registered
tests/Aspire.Cli.Tests/Utils/TelemetryOutputFormatterTests.cs	Comprehensive tests for CLI telemetry output formatting
tests/Aspire.Cli.Tests/Utils/FilterFieldValidatorTests.cs	Tests for validating filter fields against available telemetry fields
tests/Aspire.Cli.Tests/Utils/FilterExpressionParserTests.cs	Tests for parsing filter expressions with various operators
tests/Aspire.Cli.Tests/Utils/CliTestHelper.cs	Registers new telemetry command services for testing
tests/Aspire.Cli.Tests/Mcp/*.cs	Schema tests for new MCP tools (ListTraces, GetTrace, ListMetrics, etc.)
tests/Aspire.Cli.Tests/Commands/*.cs	Command tests for new telemetry CLI commands
src/Aspire.Dashboard/Mcp/McpExtensions.cs	Registers new AspireFieldsMcpTools and AspireMetricsMcpTools
src/Aspire.Dashboard/Mcp/AspireTelemetryMcpTools.cs	Adds filtering and get_trace functionality to existing tools
src/Aspire.Dashboard/Mcp/AspireMetricsMcpTools.cs	New MCP tools for listing and querying metrics data
src/Aspire.Dashboard/Mcp/AspireFieldsMcpTools.cs	New MCP tools for discovering available telemetry fields and their values
src/Aspire.Cli/Utils/TelemetryOutputFormatter.cs	New formatter for human-readable telemetry output in CLI
src/Aspire.Cli/Utils/TelemetryCommandHelper.cs	Helper utilities for telemetry commands
src/Aspire.Cli/Resources/*.resx	Localization updates for new MCP command options

Files not reviewed (2)

• src/Aspire.Cli/Resources/McpCommandStrings.Designer.cs: Language not supported
• src/Aspire.Cli/Resources/TelemetryCommandStrings.Designer.cs: Language not supported

[davidfowl]

Very cool, we will be using it as inspiration for first class commands in #14138