Skip to content

docs(nextjs:session-replay) Clear sampling setup#14425

Merged
sergical merged 2 commits intomasterfrom
sergiydybskiy/devex-38-update-sampling-section-in-replay-doc
Jul 23, 2025
Merged

docs(nextjs:session-replay) Clear sampling setup#14425
sergical merged 2 commits intomasterfrom
sergiydybskiy/devex-38-update-sampling-section-in-replay-doc

Conversation

@sergical
Copy link
Member

@sergical sergical commented Jul 22, 2025

DESCRIBE YOUR PR

  • Adds an example configuration to Sampling section of Session Replay docs
  • Updates lazy loading docs to separate code blocks to be less confusing

Before/After Screenshots

Before After
Screenshot 2025-07-22 at 2 40 58 PM Screenshot 2025-07-22 at 2 41 26 PM
No sample, no example of usage Example with table for usage
Screenshot 2025-07-22 at 2 42 07 PM Screenshot 2025-07-22 at 2 41 59 PM
Same code block makes it seem like it should be in the same file Separate the blocks to make sure it's clear that they will be in 2 separate places

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

@linear
Copy link

linear bot commented Jul 22, 2025

@vercel
Copy link

vercel bot commented Jul 22, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sentry-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 22, 2025 6:59pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
develop-docs ⬜️ Ignored (Inspect) Jul 22, 2025 6:59pm

@codeowner-assignment codeowner-assignment bot requested a review from a team July 22, 2025 18:52
@sergical sergical changed the title Sergiydybskiy/devex 38 update sampling section in replay doc docs(nextjs:session-replay) Clear sampling setup Jul 22, 2025
@sfanahata sfanahata self-requested a review July 22, 2025 19:00
@sergical sergical marked this pull request as ready for review July 22, 2025 19:08
Copy link
Member

@nikolovlazar nikolovlazar left a comment

Choose a reason for hiding this comment

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

both are good points!

Copy link
Contributor

@sfanahata sfanahata left a comment

Choose a reason for hiding this comment

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

Looks great. Nice adds! I love the table in the sampling section.

@sergical sergical merged commit c1d5492 into master Jul 23, 2025
13 checks passed
@sergical sergical deleted the sergiydybskiy/devex-38-update-sampling-section-in-replay-doc branch July 23, 2025 00:00
lucas-zimerman pushed a commit that referenced this pull request Jul 29, 2025
<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR

- Adds an example configuration to Sampling section of Session Replay
docs
- Updates lazy loading docs to separate code blocks to be less confusing

### Before/After Screenshots

| Before | After |
|--------|-------|
| <img width="2056" height="1247" alt="Screenshot 2025-07-22 at 2 40
58 PM"
src="https://github.com/user-attachments/assets/6f8d3a33-6847-4ed7-aaa2-be546ab54e00"
/> | <img width="2056" height="1247" alt="Screenshot 2025-07-22 at 2 41
26 PM"
src="https://github.com/user-attachments/assets/09b75ed0-32af-493a-8c5c-4383ddc70d28"
/> |
| *No sample, no example of usage* | *Example with table for usage* |
| <img width="774" height="425" alt="Screenshot 2025-07-22 at 2 42
07 PM"
src="https://github.com/user-attachments/assets/4d31fe5b-010f-4b8f-81ba-10bb0f6f1d00"
/> | <img width="760" height="518" alt="Screenshot 2025-07-22 at 2 41
59 PM"
src="https://github.com/user-attachments/assets/c0469884-5947-4a0b-b698-fb3430432690"
/> |
| *Same code block makes it seem like it should be in the same file* |
*Separate the blocks to make sure it's clear that they will be in 2
separate places* |

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
@github-actions github-actions bot locked and limited conversation to collaborators Aug 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants