diff --git a/docs/platforms/javascript/common/data-management/data-collected/index.mdx b/docs/platforms/javascript/common/data-management/data-collected/index.mdx index 4197f17a1a69c..03962fab4a67f 100644 --- a/docs/platforms/javascript/common/data-management/data-collected/index.mdx +++ b/docs/platforms/javascript/common/data-management/data-collected/index.mdx @@ -98,7 +98,11 @@ Without `dataCollection` (and with `sendDefaultPii` unset or `false`), Sentry on - When `dataCollection` is used, HTTP body collection is enabled by default, so Form Data can be sent with `captureActionFormDataKeys` in the Remix server-side configuration. When not using `dataCollection`, this requires the deprecated `sendDefaultPii: true`. + Remix action form data is captured when `dataCollection.httpBodies` includes `"incomingRequest"`, which is the default. All form fields are captured, and values with a sensitive-looking field name (like `password` or `token`) are replaced with `[Filtered]`. + + To capture only specific fields, set `captureActionFormDataKeys` in the Remix server-side configuration. This option works on its own and doesn't require `dataCollection.httpBodies` to include `"incomingRequest"`. To stop capturing form data, remove `captureActionFormDataKeys` and exclude `"incomingRequest"` from `dataCollection.httpBodies`. + + Captured fields are sent as `remix.action_form_data.` span attributes. Before version 11, the Node.js SDK sent them as `formData.`, so update any dashboards, alerts, or saved searches that query the old attribute names.