-
Notifications
You must be signed in to change notification settings - Fork 483
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
Relay issue after some time #1250
Comments
This issue is stale because it has been open for 30 days with no activity. |
Am on it, have the same issue |
Hello 👋 @leokster, Do you have this error with some Snuba troubles ? 🤔 |
@TartanLeGrand what do you mean? |
In our case, we have the error on the relay but it's Snuba that has the problem. |
Small sidenote for @leokster; setting the modr to proxy, instead of managed will mean it won't do datascrubbing anymore. Highly discouraged as you will get sensitive data logged such as user passwords. It took us months before we noticed this and changed back to managed mode. We changed some settings in the SDK to temp scrub sensitive fields there in the mean time |
I created the ticket in the official get-sentry project but it seems to be related to the helm deployment:
getsentry/self-hosted#3016
After few minutes (~30) the logging events for this project doesn't work anymore. Events still get sent to the envelope endpoint and I receive a event ID. All services are healthy and no single container crashes. The events just disappear. If I then create a new project and change the DSN everything works again and events get logged to the new project again for some time until it fails again.
I found a workaround by setting the relay mode to proxy but this is probably not the best thing to do.
The text was updated successfully, but these errors were encountered: