[docs] Update Aspire 13.5 what's new: trace detail span pane navigation fix#1250
Conversation
Documents the fix for the span detail pane persisting across trace navigation in the dashboard (microsoft/aspire#18146). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
There was a problem hiding this comment.
Pull request overview
Updates the Aspire 13.5 release notes to document a dashboard trace-detail UX fix: the span details pane no longer persists with stale data when navigating between traces, and ?spanId= deep-links reopen the correct span.
Changes:
- Added a release-note bullet under 📊 Dashboard and telemetry improvements describing the trace navigation/span pane behavior fix.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Friendly health check error messages**: Health check failures now display concise, actionable messages instead of raw exception stacks. | ||
| - **Fixed telemetry streaming with resource filters**: Streams now wait for resources to appear before returning empty results. | ||
| - **Fixed duplicate replica display names**: Dashboard now uses the last 8 characters of the service.instance.id GUID to prevent collisions. | ||
| - **Trace detail span pane closes on navigation**: When navigating between traces (for example, using the browser's Back button or following a span link to another trace), the span detail pane now correctly closes instead of persisting with a stale span from the previous trace. If the destination URL includes a `?spanId=` query parameter, the correct span is automatically re-opened. |
|
[docs-from-code-ci-note] CI has been retriggered multiple times and is still failing due to the current PR changes (not a transient runner issue). Please update the PR changes to fix the failing checks. |
|
We've retriggered CI multiple times, and the current failures appear tied to changes in this PR rather than a transient pipeline issue. This likely needs a fix in the PR branch before CI will pass. |
|
We've retriggered CI several times, and the current failures appear to be caused by changes in this PR rather than a transient runner issue. This likely needs updates in the PR content/code to get green checks. |
|
[docs-from-code-ci] CI has been retriggered multiple times and is still failing. This appears to be due to the current PR changes rather than a transient infrastructure issue. |
|
CI has been retriggered multiple times and is still failing for this PR (latest failures: 'CI' (attempt 8)). This likely needs changes in the PR itself rather than another rerun. |
|
CI has already been retriggered many times here, and the current failure still looks content-related rather than transient. Latest failing signal: link validation is failing in |
|
This PR has had CI retriggered multiple times and is still failing on PR-specific checks. It likely needs a change in this PR to pass. |
|
[docs-from-code automation] repeated-rerun-note |
|
We've retriggered CI many times on this PR and it's still failing. At this point, the failure likely comes from changes in this PR rather than transient CI flakiness, so this probably needs a content/code fix in the PR itself. |
|
CI has failed repeatedly on this docs-from-code PR after multiple reruns, and the failures appear to be related to the changes in this PR. Please review and adjust the PR content so the checks can pass. |
|
CI has been retriggered multiple times on this PR and is still failing. The failures appear tied to the current PR changes rather than a transient runner issue, so this likely needs an update in the PR content before CI will pass. |
Documents changes from microsoft/aspire#18146
PR author:
@JamesNKTarget branch:
release/13.5— targeting this branch based on the source PR milestone13.5(exact match onmicrosoft/aspire.dev).Why this PR is needed
PR microsoft/aspire#18146 fixed a user-visible bug in the dashboard's trace detail page: when navigating between traces (e.g., pressing the browser's Back button or following a cross-trace span link), the span detail pane was left open showing a stale span from the previous trace. The fix clears the selected span when the trace changes, and if the new URL includes a
?spanId=query parameter the correct span is re-opened automatically.This behavior change is user-facing and belongs in the 13.5 release notes.
What changed
Added a bullet to the 📊 Dashboard and telemetry improvements section of
src/frontend/src/content/docs/whats-new/aspire-13-5.mdxdescribing the fix.Files modified
src/frontend/src/content/docs/whats-new/aspire-13-5.mdx— updated (added one bullet to the Dashboard section)