Sad Panda

I'd like to vote for this one. Having non-compliant JSON makes no sense.

We had a similar issue: Alerts were not triggered after conditions were clearly met. Checking logs revealed we had an issue with Kafka documented here: https://develop.sentry.dev/self-hosted/troubleshooting/#kafka

I experienced a similar issue recently: Sentry consumed all available RAM and caused system to cripple with endless OOM-killer events. Restarting Sentry helped for several hours before the issue came...

I am no expert either, I just came across this article when searched for solution: https://yuretspro.medium.com/on-premise-sentry-under-the-high-load-how-to-stay-up-running-be6a0a33791f

Yes, I have install logs. And there were no errors during upgrade.

Unfortunately, I am not a database expert. Can you please help me figure out which commands I need to execute to verify and fix the issue? Please note that I...

Here's what I see: ``` postgres=# select max(id) from sentry_environmentproject; max -------- 792802 (1 row) postgres=# SELECT nextval('sentry_environmentproject_id_seq'); nextval --------- 799322 (1 row) ```

I'd like to highlight that @roock most probably having a different issue. I didn't have any errors during the upgrade. Everything went smoothly, no errors, no warnings. I didn't run...

This is a serious issue and it hasn't been fixed. Please reopen and set appropriate status so it won't automatically close again.

I've just got the same issue while upgrading from 23.12.1 to 24.5.0. Can you please reopen this issue and find a proper fix for it?