[docs] Document dashboard connection lost message for otel logs/spans --follow

[aspire-repo-bot]

Documents changes from microsoft/aspire#20542

@JamesNK

Target branch: Targeting release/17.0 based on the source PR milestone 17.0.

Why

microsoft/aspire#20542 reduces AppHost log noise and adds a new user-visible behavior: when aspire otel logs --follow or aspire otel spans --follow is streaming and the dashboard connection closes (an expected disconnect, such as dashboard shutdown or a truncated chunked response), the CLI now prints "The connection to the dashboard was lost." to stderr and exits successfully, instead of surfacing a raw I/O exception. This is implemented by StreamReader.ReadLinesWithDisconnectHandlingAsync and the new TelemetryCommandStrings.DashboardConnectionLost resource string, and is covered by TelemetryFollowTests.

The other changes in the source PR (auxiliary backchannel disconnect handling in aspire ps, resource-readiness log suppression, HTTP client factory log filtering) only reduce internal Debug-level log noise on paths that were never documented, so no further doc updates were needed for those.

What changed

• src/frontend/src/content/docs/reference/cli/commands/aspire-otel-logs.mdx: Updated the -f, --follow option description to note the new dashboard-disconnect message and successful exit behavior.
• src/frontend/src/content/docs/reference/cli/commands/aspire-otel-spans.mdx: Same update for the aspire otel spans command.

Both are updates to existing pages; no new pages were created.

Generated by PR Documentation Check for #20542 · copilot · auto · 91.2 AIC · ⌖ 15.7 AIC · ⊞ 20.3K · ◷

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1819. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.