fix(rum): drop browser-extension "Object Not Found Matching Id" errors - #1433
Merged
Merged
Conversation
A browser extension injects `Object Not Found Matching Id:N, MethodName:update, ParamCount:4` as a bare thrown string (RUM records type: null, no stack). Only the few sessions whose user has the extension installed emit it, but each emits hundreds: on 2026-07-09, 2 sessions produced ~1160 events in 24h, doubling total RUM error volume without pointing at any Studio bug. Drop it in the beforeSend filter, matching the stable signature, alongside the other connectivity/noise drops. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request adds logic to discard browser-extension-injected 'Object Not Found Matching Id' errors in Datadog RUM events, preventing them from inflating error volumes. It includes a regex-based check in shouldKeepEvent.ts and corresponding regression tests in shouldKeepEvent.test.ts. There are no review comments, and I have no feedback to provide.
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
1 participant
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.
Summary
Adds a
beforeSendfilter rule inshouldKeepEventto discard the browser-extension-injectedObject Not Found Matching Id:N, MethodName:update, ParamCount:4error from RUM.Datadog findings (last 24h, 2026-07-09)
Surfaced by the daily RUM review. This error became the #1 error by volume, and it was entirely absent in the prior 24h window:
Object Not Found Matching IdeventsCharacterization of a sampled 390 events:
/view, all app versionv2.133.0.Error: RUM recordstype: null,handling: unhandled, andstack: "No stack, consider using an instance of Error".This is the well-known signature of an error injected by a browser extension, not thrown by Studio code. A single extension-carrying session emits hundreds of them, so a couple of users nearly doubled total RUM error volume and drowned real signal in Error Tracking — without pointing at any Studio bug.
Fix
Drop events whose message matches
/Object Not Found Matching Id:\d+, MethodName:/i, alongside the existing connectivity/noise drops (timeouts #1371, 401s #1386, etc.). Added a regression test; full suite green (1226 passed).Notes
🤖 Generated with Claude Code