Skip to content

fix(agent-monitoring): don't extrapolate span errors in traces table#110837

Merged
shellmayr merged 2 commits intomasterfrom
shellmayr/fix/use-high-accuracy-queries-for-span-errors-agent-monitoring
Mar 18, 2026
Merged

fix(agent-monitoring): don't extrapolate span errors in traces table#110837
shellmayr merged 2 commits intomasterfrom
shellmayr/fix/use-high-accuracy-queries-for-span-errors-agent-monitoring

Conversation

@shellmayr
Copy link
Copy Markdown
Member

@shellmayr shellmayr commented Mar 17, 2026

  • Had a look at some examples, and there are more than a few examples that show e.g. 64 errors for a trace with 1 LLM call, and when looking at it using this branch, it is a single error. This is not tenable of course, but this PR does introduce additional latency for large orgs, because it needs to scan all of the data

Closes TET-2082

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 17, 2026
@shellmayr shellmayr requested a review from a team March 17, 2026 15:08
@linear-code
Copy link
Copy Markdown

linear-code bot commented Mar 17, 2026

@shellmayr shellmayr marked this pull request as ready for review March 17, 2026 15:08
@shellmayr shellmayr merged commit 1bce3b6 into master Mar 18, 2026
63 checks passed
@shellmayr shellmayr deleted the shellmayr/fix/use-high-accuracy-queries-for-span-errors-agent-monitoring branch March 18, 2026 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants