From 2c6e9508bdb5c48d1d02cfe019f2a2311ad0f4dc Mon Sep 17 00:00:00 2001 From: Ryan Albrecht Date: Fri, 8 Aug 2025 15:33:34 -0700 Subject: [PATCH 1/2] fix(replay): Document searchable properties `screen` and alias `screens` --- .../search/searchable-properties/session-replay.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/concepts/search/searchable-properties/session-replay.mdx b/docs/concepts/search/searchable-properties/session-replay.mdx index 53371e46db620..1f1794046e2d3 100644 --- a/docs/concepts/search/searchable-properties/session-replay.mdx +++ b/docs/concepts/search/searchable-properties/session-replay.mdx @@ -244,6 +244,10 @@ The reason a replay was triggered. For example, `session` when `replaysSessionSa - **Type:** string +### `screen` + +A specific Screen or View that the user visited during the replay. You can also search for multiple Screens at once using `screens` and passing in an array of strings. Alias of `url`, suited for mobile. + ### `sdk.name` Name of the Sentry SDK that sent the event. @@ -271,7 +275,7 @@ A trace represents the record of the entire operation you want to measure or tra ### `url` -A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings. +A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings. Alias of `screen`, suited for web. - **Type:** string From fb41f4fe5bde0b5baae2c33d56f6105b763f9b5f Mon Sep 17 00:00:00 2001 From: Ryan Albrecht Date: Mon, 11 Aug 2025 10:24:42 -0700 Subject: [PATCH 2/2] remove "suitable" phrases, punctuation --- .../searchable-properties/session-replay.mdx | 34 ++++++++++--------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/docs/concepts/search/searchable-properties/session-replay.mdx b/docs/concepts/search/searchable-properties/session-replay.mdx index 1f1794046e2d3..280192fe72448 100644 --- a/docs/concepts/search/searchable-properties/session-replay.mdx +++ b/docs/concepts/search/searchable-properties/session-replay.mdx @@ -22,7 +22,7 @@ Replay activity is calculated based on the number of errors, the number of ui ev ### `browser.name` -Name of the users' web browser. For example, `Chrome`, `Firefox`, or `Safari` +Name of the users' web browser. For example, `Chrome`, `Firefox`, or `Safari`. - **Type:** string @@ -34,13 +34,13 @@ The version string of the browser. ### `click.alt` -The `alt` of an element that was clicked. For example, `"a good dog"` would match the element `a good dog` +The `alt` of an element that was clicked. For example, `"a good dog"` would match the element `a good dog`. - **Type:** string ### `click.class` -The `class` of an element that was clicked. No leading `.` is necessary. For example, `btn-primary` would match the element `Save` +The `class` of an element that was clicked. No leading `.` is necessary. For example, `btn-primary` would match the element `Save`. - **Type:** string @@ -54,19 +54,19 @@ Note: This property requires that your project have [React component name captur ### `click.id` -The `id` of an element that was clicked. No leading `#` is necessary. For example, `reset-password` would match the element `Reset` +The `id` of an element that was clicked. No leading `#` is necessary. For example, `reset-password` would match the element `Reset`. - **Type:** string ### `click.label` -The `aria-label` of an element that was clicked. For example, `Expand` would match the element `` +The `aria-label` of an element that was clicked. For example, `Expand` would match the element ``. - **Type:** string ### `click.role` -The `role` of an element that was clicked. For example, `button` would match both `` and `Submit` +The `role` of an element that was clicked. For example, `button` would match both `` and `Submit`. - **Type:** string @@ -78,25 +78,25 @@ An element identified using a subset of CSS selector syntax. For example, `#sect ### `click.tag` -The tag name of an element that was clicked. For example, `input` would match `` +The tag name of an element that was clicked. For example, `input` would match ``. - **Type:** string ### `click.testid` -The `data-testid` or `data-test-id` of an element that was clicked. For example, `user-name` would match the element `User Name` +The `data-testid` or `data-test-id` of an element that was clicked. For example, `user-name` would match the element `User Name`. - **Type:** string ### `click.textContent` -The immediate `textContent` of an element that was clicked. For example, `Save` would match `` but wouldn't match `` +The immediate `textContent` of an element that was clicked. For example, `Save` would match `` but wouldn't match ``. - **Type:** string ### `click.title` -The `title` of an element that was clicked. For example, `Save this comment` would match the element `Save` +The `title` of an element that was clicked. For example, `Save this comment` would match the element `Save`. - **Type:** string @@ -144,7 +144,7 @@ Similar to the `click.selector` search property, but only queries on [dead click ### `device.brand` -Brand of the device +Brand of the device. - **Type:** string @@ -162,7 +162,7 @@ Internal hardware revision to identify the device exactly. ### `device.name` -Details of the device +Details of the device. - **Type:** string @@ -204,7 +204,7 @@ Severity of the event (such as: fatal, error, warning). Always set to info for t ### `os.name` -The name of the operating system. For example, `Windows`, `Mac OS X`, or `Linux` +The name of the operating system. For example, `Windows`, `Mac OS X`, or `Linux`. - **Type:** string @@ -246,7 +246,8 @@ The reason a replay was triggered. For example, `session` when `replaysSessionSa ### `screen` -A specific Screen or View that the user visited during the replay. You can also search for multiple Screens at once using `screens` and passing in an array of strings. Alias of `url`, suited for mobile. +A specific Screen or View that the user visited during the replay. You can also search for multiple Screens at once using `screens` and passing in an array of strings. +Alias: `url` ### `sdk.name` @@ -275,7 +276,8 @@ A trace represents the record of the entire operation you want to measure or tra ### `url` -A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings. Alias of `screen`, suited for web. +A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings. +Alias: `screen` - **Type:** string @@ -305,7 +307,7 @@ Full name of the country of the user's geolocation. ### `user.geo.subdivision` -Full name of the subdivision of the user's geolocation. (For example, state, province, etc.) +Full name of the subdivision of the user's geolocation. (For example, state, province, etc.). - **Type:** string