Hubert Deng

@szokeasaurusrex What do you think about this?

That is indeed interesting. I'm seeing `Net Exception: Socket is not connected, Stack trace` in your clickhouse logs? Maybe your Sentry instance lost connection there?

Unsure why this is only happening for post-process-forwarder, since I don't think that was converted to rust-consumer. Wondering if we are missing a ` --no-strict-offset-reset` on the `post-process-forwarder` containers. Could...

Thanks for reporting here. I do not think you should rely on the /_health/ endpoint in Sentry as a source of truth, I just took a look and it seems...

Thanks for chiming in. I do not think this should affect how the cleanup job works, but it is a bug nonetheless.

nvm, stats page fix should be here: https://github.com/getsentry/self-hosted/pull/2909

I'm going to keep this open for now and merge if folks are still experiencing issues with transactions

@zKoz210 is this after switching to rust python transactions consumer? Or using the python transactions python consumer?

@jawabuu Were you able to get this working? If so, do you mind sharing what your workflow is?

Transferring to self-hosted, but not prioritizing this