Skip to content

Commit

Permalink
feat(JS): Add normalizeMaxBreadth option (#4844)
Browse files Browse the repository at this point in the history
This documents the new `normalizeMaxBreadth` option added to JS-based SDKs in getsentry/sentry-javascript#4689, which controls how many properties or entries any given object or array will contain after normalization.
  • Loading branch information
lobsterkatie authored Mar 22, 2022
1 parent ccb0eaa commit 6733b4e
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion src/platforms/common/configuration/options.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -352,7 +352,15 @@ Maximum number of characters a single value can have before it will be truncated

<ConfigKey name="normalize-depth" supported={["javascript", "node"]}>

Sentry SDKs normalize any contextual data to a given depth. Any keys containing data with a structure deeper than this will be trimmed and marked using its type instead (`[Object]` or `[Array]`), without walking the tree any further. By default, walking is performed `3` levels deep.
Sentry SDKs normalize any contextual data to a given depth. Any data beyond this depth will be trimmed and marked using its type instead (`[Object]` or `[Array]`), without walking the tree any further. By default, walking is performed three levels deep.

</ConfigKey>

<ConfigKey name="normalize-max-breadth" supported={["javascript", "node"]} notSupported={["react-native", "electron"]}>

_(New in version 6.19.1)_

This is the maximum number of properties or entries that will be included in any given object or array when the SDK is normalizing contextual data. Any data beyond this depth will be dropped. (defaults to 1000)

</ConfigKey>

Expand Down

1 comment on commit 6733b4e

@vercel
Copy link

@vercel vercel bot commented on 6733b4e Mar 22, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

Please sign in to comment.