Skip to content

Update explore dashboard page with new content and screenshots where needed #2617

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JamesNK opened this issue Feb 13, 2025 · 2 comments · Fixed by #3125
Closed

Update explore dashboard page with new content and screenshots where needed #2617

JamesNK opened this issue Feb 13, 2025 · 2 comments · Fixed by #3125
Labels
📦 release-9.1 Used to track doc updates for release 9.1 of .NET Aspire. ⌚ Not Triaged Not triaged

Comments

@JamesNK
Copy link
Member

JamesNK commented Feb 13, 2025

Describe the issue or suggestion

That are a lot of minor dashboard features in 9.1. The explore dashboard page should be updated to reflect the new state of the dashboard.

I tweet a range of changes that a user will see on twitter/bluesky (daily dashboard feature series). It's a good place to look to see how changes impact the user.

@dotnetrepoman dotnetrepoman bot added the ⌚ Not Triaged Not triaged label Feb 13, 2025
@danmoseley danmoseley added the 📦 release-9.1 Used to track doc updates for release 9.1 of .NET Aspire. label Feb 19, 2025
@alistairmatthews
Copy link
Contributor

#3125 adds pausing and removing telemetry data. Also filtering spans in a trace. Some screenshots updated to 9.2.0.

@JamesNK are there any other specific features you want added? I didn't want to go super-deep as it's only an explore article.

@JamesNK
Copy link
Member Author

JamesNK commented Apr 17, 2025

Added two bits of feedback: #3125 (comment)

Other than those changes, looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 release-9.1 Used to track doc updates for release 9.1 of .NET Aspire. ⌚ Not Triaged Not triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants