Skip to content

docs: Document Error Tracking weekly digest per-project settings#15372

Open
inkeep[bot] wants to merge 2 commits intomasterfrom
docs-writer-ai-update-2026-02-27T12-24-07-812Z-4dwoxf
Open

docs: Document Error Tracking weekly digest per-project settings#15372
inkeep[bot] wants to merge 2 commits intomasterfrom
docs-writer-ai-update-2026-02-27T12-24-07-812Z-4dwoxf

Conversation

@inkeep
Copy link
Contributor

@inkeep inkeep bot commented Feb 27, 2026

Summary

This PR documents the Error Tracking weekly digest feature improvements from PostHog/posthog#49243.

Changes

contents/docs/settings/account-settings.mdx

  • Expanded the Notifications section to list all available notification types
  • Added a dedicated "Error Tracking weekly digest" subsection documenting:
    • Weekly email sent every Monday summarizing exceptions across projects
    • Per-project settings allowing users to select which projects to include
    • Auto-selection behavior: if no projects are manually selected, PostHog picks the busiest project on first run

contents/docs/error-tracking/alerts.mdx

  • Added a "Weekly digest emails" subsection under "Other alerting options"
  • Documents the weekly digest as another notification option alongside real-time alerts
  • Links to the notification settings for configuration

Feature details from PR #49243

The feature PR introduced these user-facing changes:

  1. One email per org - Weekly digest now sends one email per organization with sections for each project
  2. Per-project notification settings - Users can select which specific projects to receive the digest for
  3. Auto-selection - For first-time users who haven't selected projects, the system automatically picks the project with the most exceptions
  4. Full release - The Error Tracking weekly digest feature is now fully released (feature flag removed)

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.

inkeep bot added 2 commits February 27, 2026 12:25
…details

Adds a list of all available notification types and a dedicated subsection
for the Error Tracking weekly digest covering per-project controls and
auto-selection behavior. Based on PostHog/posthog#49243.
Documents the fully released Error Tracking weekly digest feature,
including per-org emails with per-project sections, auto-selection
of busiest project, and link to notification settings.
@inkeep inkeep bot requested a review from ablaszkiewicz February 27, 2026 12:27
@github-actions
Copy link
Contributor

github-actions bot commented Feb 27, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Feb 27, 2026 12:39PM

@github-actions
Copy link
Contributor

Vale prose linter → found 8 errors, 8 warnings, 2 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/error-tracking/alerts.mdx — 0 errors, 5 warnings, 1 suggestions
Line Severity Message Rule
2:13 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
9:55 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
9:61 warning 'tracking's' is a possible misspelling. PostHogBase.Spelling
37:7 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
43:47 warning Capitalize 'Data Pipelines' for PostHog's product. Use 'data pipelines' for the general industry concept. PostHogBase.ProductNames
69:37 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
contents/docs/settings/account-settings.mdx — 8 errors, 3 warnings, 1 suggestions
Line Severity Message Rule
29:34 warning 'zxcvbn' is a possible misspelling. PostHogBase.Spelling
30:41 warning 'NIST's' is a possible misspelling. PostHogBase.Spelling
33:4 warning 'Enabling 2FA' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
45: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
46: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
47: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
48: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
49: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
50: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
51: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
52: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
66:79 suggestion Prefer 'proper nouns or them' over 'him'. PostHogBase.Inclusivity

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.

0 participants