Skip to content

fix(detectors): Use correct key for transaction name#120118

Merged
lobsterkatie merged 1 commit into
masterfrom
kmclb-fix-getting-transaction-name-in-existing-detectors
Jul 20, 2026
Merged

fix(detectors): Use correct key for transaction name#120118
lobsterkatie merged 1 commit into
masterfrom
kmclb-fix-getting-transaction-name-in-existing-detectors

Conversation

@lobsterkatie

Copy link
Copy Markdown
Member

This fixes a bug in a few of the existing issue detectors which is causing a false positive mismatch in the existing-vs-span-first-detectors experiment. In most of the existing detectors, we correctly look at event["transaction"] to get the value for evidence_data.transaction_name, but in a few we instead look at event["description"], even though events have never had a top-level description field. (The fact that this mistake is replicated across four detectors appears to just be copy-pasta.)

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 20, 2026
@lobsterkatie
lobsterkatie marked this pull request as ready for review July 20, 2026 20:00
@lobsterkatie
lobsterkatie requested a review from a team as a code owner July 20, 2026 20:00
@lobsterkatie
lobsterkatie merged commit 5e98be0 into master Jul 20, 2026
74 checks passed
@lobsterkatie
lobsterkatie deleted the kmclb-fix-getting-transaction-name-in-existing-detectors branch July 20, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants