[✨ Triage] dotnet/aspire#11770 by KalleOlaviNiemitalo - Clear resources (service.instance.id) from dashboard

[MihuBot]

Triage for dotnet/aspire#11770.
Repo filter: area-dashboard issues.
MihuBot version: 554101.
Ping MihaZupan for any issues.

This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.

Tool logs

dotnet/aspire#11770: Clear resources (service.instance.id) from dashboard by KalleOlaviNiemitalo
[Tool] Searching for Remove all button dashboard, clear resources dashboard, service.instance.id dashboard, resource selector dashboard, remove filters dashboard (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=False, Repository=dotnet/aspire)
[Tool] Searching for issue 9040 (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Searching for issue 11769 (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 6 issues, 24 comments, 3 returned results (10593 ms)
[Tool] Found 4 issues, 0 comments, 1 returned results (11654 ms)
[Tool] Found 71 issues, 182 comments, 40 returned results (13582 ms)

Here are the related issues and discussions for issue #11770 "Clear resources (service.instance.id) from dashboard":

---

Highly Related Issues

Issue #9040 (April 2025) - ""Remove all" should reset all applied filters"

• Summary: This issue requests that the "Remove all" button in the dashboard should also reset all active filters, not just remove telemetry. The discussion clarifies that "Remove all" currently only removes telemetry, not filters, and there is debate about whether removing filters is expected behavior. A suggestion is made to add a "Reset all state" button for broader resets.
• Relevance: The issue mentions filters, not resources, but is referenced in #11770 as a similar UX concern. The solution proposed in #11770 (clearing resources) is distinct but related in terms of dashboard state management.

Issue #11769 (October 2025) - "Cannot select specific resource instance in standalone dashboard"

• Summary: This issue describes a problem where selecting a specific resource instance (distinguished by service.instance.id) in the dashboard's resource selector does not work as expected—the selection flashes and then resets to "(All)" or "(None)". The issue is referenced in #11770 as a motivation for wanting to clear old resource IDs.
• Relevance: Directly related; clearing resources would help work around the selection problem described here.

Issue #5458 (August 2024, closed Feb 2025) - "Add clear button to dashboard console logs page"

• Summary: Requests a clear button for console logs, with discussion about extending this to all logs/traces/metrics. PR #6898 added clear buttons for structured logs/traces/metrics, but not console logs.
• Relevance: Shows ongoing work to improve dashboard clearing functionality, though not specifically about resource selectors.

Issue #7488 (Feb 2025, closed Feb 2025) - "Clear all button in settings should clear console logs"

• Summary: Suggests that the "Clear all" button should also clear console logs, not just telemetry. No discussion about resources.
• Relevance: Related to dashboard clearing semantics, but not directly about resource selectors.

Issue #2776 (March 2024, closed March 2024) - "[BUG] The .NET Aspire dashboard resource filter doesn't remove selections"

• Summary: When filtering resources, the selected detail view isn't reset if the resource is filtered out. Discussion is about selection state, not resource persistence.
• Relevance: Related to dashboard UX around resource selection and filtering.

Issue #11257 (Sept 2025, closed Sept 2025) - "resource filter not work when aspire dashboard standalone deployment"

• Summary: Reports that resource filtering does not work in standalone dashboard deployment. The issue was resolved by updating to a newer version.
• Relevance: Related to resource selector/filtering bugs in the dashboard.

---

Other Related Issues

Issue #1190 (Dec 2023, closed Jan 2025) - "Filter resources with errors on dashboard"

• Summary: Requests filtering resources by state (e.g., errors) in the dashboard. Discussion about improving filtering UX.
• Relevance: Shows interest in more flexible resource filtering, but not about clearing resource history.

Issue #4628 (June 2024, closed April 2025) - "Consider filtering dashboard by state"

• Summary: Requests ability to filter out resources by state (e.g., "Finished") or category.
• Relevance: Related to resource visibility, not persistence.

Issue #896 (Nov 2023) - "Standardize sorting, filtering, & searching UX for dashboard views"

• Summary: Requests standardized filtering/searching UX across dashboard views.
• Relevance: Related to dashboard filtering, not resource persistence.

Issue #2566 (March 2024, closed March 2024) - "Dashboard resource dropdowns max height"

• Summary: Requests limiting the height of resource dropdowns to avoid UI overflow.
• Relevance: UI improvement for resource selectors.

Issue #4217 (May 2024, closed July 2024) - "Standalone Mode - Data being aggregated under a single application service name"

• Summary: Discusses how the dashboard aggregates telemetry based on service.instance.id and service.name, leading to confusion when multiple apps have the same instance ID. Workarounds are suggested.
• Relevance: Explains dashboard logic for resource grouping, relevant to why stale instance IDs may persist in selectors.

---

Key Points from Discussions

• Current Behavior: The "Remove all" button only removes telemetry data, not filters or resource selector history. This is confirmed in #9040.
• Resource Selector Persistence: Old service.instance.id values remain in the resource selector dropdown even after telemetry is cleared, leading to UI clutter and confusion.
• Related Bugs: Issue #11769 describes problems with selecting specific resource instances, which would be mitigated by clearing old resource IDs.
• Suggested Solutions: There is precedent for adding broader reset functionality (e.g., "Reset all state" button) to the dashboard, but no existing solution for clearing resource selector history.
• Workarounds: Some users manually adjust their telemetry configuration to avoid resource selector clutter (#4217).

---

Summary

• There is no existing issue or PR that implements the requested feature: clearing resource selector history (e.g., old service.instance.id values) when "Remove all" is pressed.
• The closest related issues are about clearing telemetry, filters, or improving resource selector/filtering UX, but none address resource persistence in selectors.
• The problem described in #11770 is a recognized gap in dashboard functionality, and the proposed solution (clearing resource history) would be a new feature.

---

Recommendation

• Reference issues #9040 and #11769 for related dashboard clearing/filtering semantics and resource selector bugs.
• Consider opening a new feature request or PR to extend the "Remove all" button to also clear resource selector history, or to add a dedicated button for this purpose.

---

If you need a more detailed breakdown of any specific issue or want to see full comment threads, let me know!