PostHog / PostHog/posthog-android
Apply error-tracking suppression rules from remote config
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 90
- Forks
- 49
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 61
Description
Extracted from PostHog/posthog#43012.
Problem
Suppression rules already ship end to end (backend model, API, remote-config delivery, settings UI) and posthog-js enforces them, but the Android SDK ignores errorTracking.suppressionRules, so rules set in the UI don't affect Android events.
Scope
- Read
suppressionRulesfrom remote config, persist them, and drop matching exceptions before capture. - Match on
$exception_listtype and value with the same operator and AND/OR semantics as the web SDK (posthog-jspackages/browser/src/posthog-exceptions.ts).
SDK only, no backend or frontend work. The web matcher currently ignores the per-rule samplingRate (boolean drop only); match that for now.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced matcher in packages/browser/src/posthog-exceptions.ts to understand the operators and AND/OR semantics, including its boolean-only treatment of samplingRate. Then trace Android remote-config delivery, persistence, and exception capture; done means matching suppressionRules cause Android exceptions to be dropped before capture.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100