Skip to content

docs(javascript): Change default value for maxValueLength #15349

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 31, 2025
Merged

docs(javascript): Change default value for maxValueLength #15349

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/platforms/javascript/common/configuration/options.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Sentry.init({

</SdkOption>

<SdkOption name="maxValueLength" type='number' defaultValue='250'>
<SdkOption name="maxValueLength" type='number'>

Maximum number of characters every string property on events sent to Sentry can have before it will be truncated.

Expand Down
6 changes: 3 additions & 3 deletions docs/platforms/javascript/common/troubleshooting/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ For more details, see the [full documentation on Event Payload](https://develop.

<Expandable permalink title="Max JSON payload size">

`maxValueLength` has a default value of 250, but you can adjust this value according to your needs if your messages are longer. Please note that not every single value is affected by this option.
By default, `maxValueLength` is undefined and nothing is truncated, but you can change this value according to your needs if your messages are longer (for example, to `250`). Please note that not every single value is affected by this option.

</Expandable>

Expand Down Expand Up @@ -670,10 +670,10 @@ shamefully-hoist=true
```

</Expandable>

<Expandable permalink title="Client Instrumentation Hook - Slow execution detected">
Seeing this warning in your dev build might be misleading due to Next.js dev server internals.

In case you are using Session Replay and experience performance issues with the client instrumentation hook, you can try lazy-loading session replay as described [here](/platforms/javascript/guides/nextjs/session-replay/#lazy-loading-replay).

If you want to init the SDK itself at a later point, this will result in tracing data loosing accuracy and errors could happen before the SDK is initialized. This should be a tradeoff you make based on your use case, although we recommend initializing the SDK as early as possible.
Expand Down
Loading