feat(seer): Steer low-value span root cause analysis#116671
Draft
ArthurKnaus wants to merge 1 commit into
Draft
Conversation
Teach Autofix root cause analysis to treat low-value span issues as Sentry-created optimization guidance instead of exception-style failures. Keep the normal step flow while adding concise issue-specific context for low-value spans. Co-Authored-By: Codex <codex@openai.com>
Contributor
Backend Test FailuresFailures on
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Steer Autofix root cause analysis for low-value span issues so Seer treats them as Sentry created optimization guidance instead of exception-style failures. This keeps the normal Autofix step flow while giving root cause analysis enough issue-specific context to use the latest occurrence evidence correctly.
Currently the root cause analysis tries to handle this type of issue as if it is an exception in the user's codebase, not understanding it is an issue created by Sentry to notify users about optimization potential. Low-value span RCA now explains that the root cause is a high-volume span with low telemetry value.
Part of TET-2194