docs(javascript): Session Replay Sampling clarification

Author: sergical

docs/platforms/javascript/common/session-replay/index.mdx

@@ -157,6 +157,20 @@ Sampling allows you to control how much of your website's traffic will result in
    record up to a minute of events prior to the error and continue recording
    until the session ends.
 
+### Recommended Sample Rate Values
+
+**For Development/Testing:**
+- `replaysSessionSampleRate: 1.0` (100%) - Capture all sessions for complete visibility
+- `replaysOnErrorSampleRate: 1.0` (100%) - Capture all error sessions
+
+**For Production:**
+- `replaysSessionSampleRate: 0.01` (1%) for high-traffic sites (100k+ sessions/day)
+- `replaysSessionSampleRate: 0.1` (10%) for medium-traffic sites (10k-100k sessions/day)
+- `replaysSessionSampleRate: 0.25` (25%) for low-traffic sites (under 10k sessions/day)
+- `replaysOnErrorSampleRate: 1.0` (100%) - Always capture sessions with errors for debugging
+
+### How Sampling Works
+
 Sampling begins as soon as a session starts. <PlatformIdentifier name="replays-session-sample-rate" /> is evaluated first. If it's sampled, the replay recording will begin. Otherwise, <PlatformIdentifier name="replays-on-error-sample-rate" /> is evaluated and if it's sampled, the integration will begin buffering the replay and will only upload it to Sentry if an error occurs. The remainder of the replay will behave similarly to a whole-session replay.
 
 ## Error Linking