Feat/posthog error tracking redaction#329
Open
laxmanclo wants to merge 5 commits into
Open
Conversation
laxmanclo
force-pushed
the
feat/posthog-error-tracking-redaction
branch
from
a991dac to
ccc9e8b
Compare
laxmanclo
force-pushed
the
feat/posthog-error-tracking-redaction
branch
from
ccc9e8b to
6ad98a3
Compare
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
1 participant
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.
This improves telemetry without widening what we send remotely.
Renderer exceptions now go into PostHog Error Tracking(before it was just tracking the error, not capturing in depth, which gives us proper grouped UI issues. We also scrub local paths and local URLs before capture. On the backend, failures still emit as events, but now include better structured metadata like component, operation, error kind/code, and
fingerprints so they are easier to group and investigate without leaking raw internals. Backend tele can still be improved a lot, but requires lots of change.