[docs] Document consistent SQLite telemetry reads during eviction

[aspire-repo-bot]

Documents changes from microsoft/aspire#20597

@JamesNK

Target branch: Targeting release/17.0 based on the source PR milestone 17.0 (exact match found on microsoft/aspire.dev).

Why this is needed

Source PR microsoft/aspire#20597 fixed intermittent HTTP 500s and incomplete attribute/detail data in the dashboard's Traces, Spans, Structured Logs, and Metrics views, caused by telemetry eviction removing rows between dependent SQLite reads. The PR body includes an explicit "### User-facing behavior" section stating no configuration changes are required but that the views' consistency guarantees changed, which is a documented-behavior gap on microsoft/aspire.dev.

What changed

• Updated dashboard/data-persistence.mdx — added a paragraph under "Telemetry retention and disk use" explaining that dependent reads (e.g., trace + its spans, log + its attributes, metric dimensions/points/exemplars) now run inside a single deferred SQLite transaction so normal telemetry eviction can't remove a selected row mid-query. Notes that concurrent WAL ingestion is unaffected, and that cached resource/instrument metadata lookups are outside these transactions (so an explicit telemetry clear racing a cache lookup isn't covered).

Files modified

• src/frontend/src/content/docs/dashboard/data-persistence.mdx (updated existing page, no new pages)

Generated by PR Documentation Check for #20597 · copilot · auto · 58.6 AIC · ⌖ 17.3 AIC · ⊞ 20.3K · ◷

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1815. 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.