Skip to content

Conversation

@ArthurKnaus
Copy link
Member

Problem

In the AI trace we substitute the span icon with an error icon whenever there is an error on the span status or an issue connected to it. This confused users as they were not sure anymore what type of span they see.

Solution

Preserve the original icon and show the error icon additionally.
Also include a tooltip to explain the meaning of the flame / error icon.

Screen.Recording.2025-12-15.at.08.31.29.mov

@ArthurKnaus ArthurKnaus requested a review from a team as a code owner December 15, 2025 07:36
@linear
Copy link

linear bot commented Dec 15, 2025

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 15, 2025
@codecov
Copy link

codecov bot commented Dec 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #104937      +/-   ##
===========================================
- Coverage   80.52%    80.41%   -0.12%     
===========================================
  Files        9398      9393       -5     
  Lines      405708    403384    -2324     
  Branches    25923     25923              
===========================================
- Hits       326710    324383    -2327     
- Misses      78558     78561       +3     
  Partials      440       440              

@ArthurKnaus ArthurKnaus merged commit bb2a8e9 into master Dec 15, 2025
50 checks passed
@ArthurKnaus ArthurKnaus deleted the arthurknaus/tet-1576-ai-trace-view-unclear-which-span-errored-out branch December 15, 2025 09:22
@github-actions github-actions bot locked and limited conversation to collaborators Dec 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants