-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speculative logging for PostHog/posthog#4816 #293
Speculative logging for PostHog/posthog#4816 #293
Conversation
@macobo related to the issue we discussed yesterday... I think this will send an event back to posthog when the gzip bug manifests... will it? |
OK, so, very hacky approach @macobo. Like this? I'm thinking of minimal change to getting debug info for the linked issue Ultimately, if we want to keep the idea of a debug channel it feels wrong to hide this inside capture metrics. And would need to add a new "thing" so that users can more explicitly opt in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This reverts commit 5447142.
This reverts commit 5447142.
Changes
PostHog/posthog#4816 shows we intermittently receive unexpected values in place of gzipped content
this logging catches unexpected source or zipped data and logs it back to posthog
...
Checklist