[✨ Triage] dotnet/aspire#11684 by KalleOlaviNiemitalo - Recognize "http.request.method" and "http.response.status_co ...

[MihuBot]

Triage for dotnet/aspire#11684.
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#11684: Recognize "http.request.method" and "http.response.status_code" span attributes in dashboard by KalleOlaviNiemitalo
[Tool] Searching for http.request.method, http.response.status_code, OpenTelemetry semantic conventions, dashboard http.method http.status_code, dashboard span attributes (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 35 issues, 221 comments, 23 returned results (13797 ms)

Here are related issues and discussions for issue #11684, "Recognize 'http.request.method' and 'http.response.status_code' span attributes in dashboard":

---

1. No Direct Duplicates or Feature Requests Found

A thorough search did not reveal any existing issues or PRs that directly request support for the new OpenTelemetry HTTP semantic conventions (http.request.method and http.response.status_code) in the Aspire dashboard. Issue #11684 appears to be the first explicit feature request for this.

---

2. Related Discussions and Context

a. OpenTelemetry Semantic Conventions and Dashboard Support

• PR #3351 (April 2024) - Update OpenTelemetry packages to 1.8.0

  • This PR updates OTEL packages and discusses trace sampling and OTLP exporter configuration, but does not mention the new HTTP attribute names or dashboard recognition logic.
  • View PR #3351

• PR #1948 (January 2024) - Update OpenTelemetry packages and use built-in metric methods

  • Focuses on updating OTEL packages and metric methods, not on dashboard attribute recognition.
  • View PR #1948

b. Dashboard Telemetry and Attribute Handling

• PR #7884 (March–April 2025) - Implement dashboard telemetry

  • Implements telemetry for dashboard usage, but not about span attribute recognition for HTTP.
  • View PR #7884

• PR #6177 (October 2024) - Ensure unique attributes on telemetry

  • Fixes duplicate attribute handling in the dashboard, referencing the OTEL spec for attribute collections. This shows the dashboard is actively maintained for OTEL compliance, but does not mention HTTP method/status attributes.
  • View PR #6177

c. Attribute and Convention Discussions

• PR #4661 (June–July 2024) - Use uniform convention for naming and annotating DCP objects with regards to OTEL
  • Focuses on naming conventions for DCP objects and their mapping to OTEL, not HTTP span attributes.
  • View PR #4661

d. General OpenTelemetry Architecture

• PR #418 (October 2023) - Add Aspire OpenTelemetry architecture doc
  • Documents how telemetry works in Aspire and references the use of OTEL, but does not discuss specific attribute names.
  • View PR #418

---

3. Comments on Attribute Recognition Logic

• In your issue, you reference the code in src/Aspire.Dashboard/Otlp/Model/OtlpSpan.cs that only recognizes the old attribute names. No issues or PRs were found that update this logic to support the new names.

---

4. Comments on Related Issues

• Issue #2577 (March–July 2024) - Aspire Dashboard: Traces: Span links aren't shown in span details

  • Discusses missing features in the dashboard's trace display, but not HTTP attribute recognition.
  • View Issue #2577

• Issue #1416 (December 2023–September 2024) - Support filtering traces by request path

  • Discusses filtering traces by span properties, including HTTP path, but not the attribute name mapping.
  • View Issue #1416

---

5. Comments in Issue #11684

• The only comment (by the author) notes that the dashboard's friendly summary logic was added after the OTEL semantic conventions v1.21.0 release, implying the dashboard never supported the new attribute names.

---

Summary

• No existing issue or PR currently tracks adding support for http.request.method and http.response.status_code in the Aspire dashboard.
• The dashboard's attribute recognition logic is still using the old names.
• The issue is well-documented and references all relevant upstream OTEL changes and .NET runtime/aspnetcore PRs.
• There is evidence that the Aspire team is actively maintaining OTEL compliance, but this specific gap has not yet been addressed.

---

Recommendation

• Issue #11684 is a valid and new feature request. It should remain open for tracking.
• Consider referencing this issue in future PRs or discussions about dashboard OTEL compliance or HTTP span attribute support.

---

If you need a list of issues to watch for progress or want to cross-link this issue, the above are the most relevant discussions and PRs. There is no duplicate or already-in-progress fix for this specific problem.