Skip to content

docs(replay): Add warning about 100% sampling with ANY matching#17301

Open
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-06-04T20-13-57-137Z-gs783d
Open

docs(replay): Add warning about 100% sampling with ANY matching#17301
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-06-04T20-13-57-137Z-gs783d

Conversation

@inkeep
Copy link
Copy Markdown
Contributor

@inkeep inkeep Bot commented Jun 4, 2026

Changes

This PR adds a documentation warning to explain a common configuration pitfall in Session Replay recording conditions.

When users configure:

  • Match type set to "any"
  • Sampling rate at 100%
  • AND other recording conditions (URL triggers, event triggers, or feature flags)

...the 100% sampling will match every session, making the other conditions ineffective. This is now documented with a caution callout in the "Combining controls" section.

Related

Review

@ksvat - As the author of the original PR, please review this docs update.


This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

…iguration

Reflects the warning banner added in PostHog/posthog#61718 that alerts users when 100% sampling combined with "any" matching and other conditions causes all sessions to be recorded.
@inkeep inkeep Bot requested a review from ksvat June 4, 2026 20:15
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jun 04, 2026 08:28PM

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Vale prose linter → found 10 errors, 17 warnings, 1 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx — 10 errors, 17 warnings, 1 suggestions
Line Severity Message Rule
18:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
20:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
22:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
24:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
30:142 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
30:246 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
30:308 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
71:4 warning 'With Event trigger conditions' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
73:7 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
85:13 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
107:74 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
109:23 warning 'navigations' is a possible misspelling. PostHogBase.Spelling
111:9 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
132:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
132:13 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
133:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
134:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
135:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
144:142 error Use straight quotes and apostrophes, not curly ones. PostHogDocs.CurlyQuotes
144:177 error Use straight quotes and apostrophes, not curly ones. PostHogDocs.CurlyQuotes
158:125 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
176:101 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
184:154 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
200:77 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
209:107 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
222:12 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
272:24 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
281:87 warning 'navigations' is a possible misspelling. PostHogBase.Spelling

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Hey @ksvat! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant