docs(replay): Add warning about 100% sampling with ANY matching#17301
Open
inkeep[bot] wants to merge 1 commit into
Open
docs(replay): Add warning about 100% sampling with ANY matching#17301inkeep[bot] wants to merge 1 commit into
inkeep[bot] wants to merge 1 commit into
Conversation
…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.
Contributor
Deploy preview
|
Contributor
|
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!
|
| 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 |
ksvat
approved these changes
Jun 4, 2026
Contributor
|
Hey @ksvat! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
This PR adds a documentation warning to explain a common configuration pitfall in Session Replay recording conditions.
When users configure:
...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.