`aspire dashboard run` should have arguments for specify telemetry limits

[afscrome]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

It would be helpful if aspire dashboard run has arguments to specify telemetry limits

{
  "Dashboard": {
    "TelemetryLimits": {
      "MaxLogCount": 50000,
      "MaxTraceCount": 50000,
      "MaxMetricsCount": 50000
    }
  }
}

Describe the solution you'd like

Some kind of easy argument for telemetry limit

aspire dashboard run --logs-limit 50000

Maybe as this is intended for local dev, you could keep it simple and have a single --telemetry limit item rather than seperate options for each.

Additional context

Related to microsoft/aspire.dev#1033

[joperezr]

🤖 Aspire triage pass — 2026-05-21 17:16 UTC

Area: area-telemetry, area-cli
Kind: feature-request
Repro: n/a — feature request
Affected version(s): not specified (latest: 13.3.x track)
Severity: S4 — quality-of-life enhancement for aspire dashboard run; workaround exists via JSON config

Urgency: ⚪ backlog — no milestone
Reason: S4 feature request with config-file workaround; not a regression or shipping-bits bug

Suggested owner(s): @JamesNK (score ~36, dominant area-cli author last 90d)
Evidence:

• @JamesNK merged dozens of area-cli PRs in last 90d (e.g. Move error handling from Program.cs to BaseCommand SetAction delegate #17310, Move InitCommand hardcoded strings to resource file for localization #17260, Improve ConsoleCancellationManager with process termination timeout #17251, Route error-context DisplayMessage calls to stderr in BaseCommand #17231, Use grid layout in DisplayMessage/DisplayError for better text wrapping #17198, Fix flaky NewCommandChannelResolutionTests by isolating home directory #17180, Fix CLI cancellation disposal race on shutdown #17179, CLI: Print app host CLI log path when connected to a running app host #17168, Improve version log messages in CLI, AppHost and dashboard #17163, Handle canceled backchannel streams #17114)
• area-telemetry had no merged PRs in last 90d under that exact label, so signal comes from the CLI side

Confidence: medium
Needs human?: no

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.