-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Data error #18
Comments
Hi! |
Could you check |
The service that is sending the sentry-event is not a php-service, it's javascript (graphql). And since it is not a service that is under our control we cannot change the way it sends the sentry-event (without gz compression). |
Oh, now I got it. Thank you for the response! I'll try to reproduce you case and find out some solution! |
We just came across the same problem, but in our case it is a react app that sends sentry issues directly via browser. Initially we got a 404 because the Sentry API eventhandler didn't find the necessary headers. After faking the headers we got the above error (obviously). It would be awesome if buggregator could support Sentry events from JavaScript SDKs. :) |
Hey @eXaminator, Thanks for the suggestion! I've gone ahead and created a PR #73 to address this. I'll be rolling out a new Buggregator release soon. Stay tuned! |
Hi @temp I've made some tweaks to Buggregator, and I believe I've resolved an issue with Sentry. Could you please take a look and verify it? |
One of the services in our stack submits a sentry event without gz-compression, but since it is not a service from our end, we can't simply enable the gz-compression.
Version is latest dev.
I guess it should work without gz-compression, since this is plain http?
The text was updated successfully, but these errors were encountered: