-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(protocol): Add scraping_attempts field #2575
Conversation
/// Information about attempts to scrape a JS source or sourcemap file from the web. | ||
/// This field is populated by sentry. | ||
#[metastructure(omit_from_schema)] // not part of external schema | ||
pub scraping_attempts: Annotated<Array<Value>>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we make this a Value
instead of Array
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good call. Then Relay dies not even have to be updated if the sentry-side schema ever changed to an object to include more metadata, for example. Updated now.
getsentry/sentry#57461 introduced a new top-level field on the event that is only written by sentry. To prevent errors when the event passes through normalization after writing
scraping_attempts
, make sure that the new field is part of the schema known by (lib)relay.