-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Fresh install error: AssertionError sentry.eventstream.kafka.backend in _build_consumer #40120
Comments
Hm, sorry you are running into this issue. Are there any more details if you click through to the issue? I cannot reproduce this. You might also want to check if there is any hints in the docker compose logs. |
This comment was marked as off-topic.
This comment was marked as off-topic.
The rest of traceback:
|
Getting this too, with latest Weird thing is that I don't even see that error in Sentry, under the |
Did a bit of troubleshooting, added a debug log logger.info(f"topic={self.topic} transactions_topic={self.transactions_topic}") before the # /usr/local/lib/python3.8/site-packages/sentry/eventstream/kafka/backend.py:218
assert self.topic == self.transactions_topic and got
There's a comment above that says:
Not sure what that means, but maybe it helps. 🙂 |
Same here |
Seems like this may be a regression of some sort from the kafka backend on sentry, not an issue introduced recently with self-hosted. I'll be transferring this to getsentry/sentry for further investigation |
Routing to @getsentry/sns for triage. ⏲️ |
Seems like the file in question, |
Errors and transactions pipelines are fully separate now, previously they shared infra. We would need to have two separate post process forwarders, as running both in a single container is no longer supported. Errors one would need to be like: Transactions one would be like: |
Combined post process forwarder no longer works with Sentry/Snuba defaults (fully separated errors/transactions topics). Running a combined PPF caused this error in self hosted: #40120.
So I'm guessing this is how the docker-compose.yml file would look like
|
Ftr here is where we flipped the switch last week:
We're working through an attempted fix in getsentry/self-hosted#1759. |
Should be fixed in getsentry/self-hosted#1759. |
…0130) Combined post process forwarder no longer works with Sentry/Snuba defaults (fully separated errors/transactions topics). Running a combined PPF caused this error in self hosted: #40120. In the future it may be nice to support a PPF implementation that can consume from multiple topics in order to reduce the amount of docker containers in dev / low volume environments but this is not currently possible.
…0130) Combined post process forwarder no longer works with Sentry/Snuba defaults (fully separated errors/transactions topics). Running a combined PPF caused this error in self hosted: #40120. In the future it may be nice to support a PPF implementation that can consume from multiple topics in order to reduce the amount of docker containers in dev / low volume environments but this is not currently possible.
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
Version
Sentry 22.10.0.dev0
Steps to Reproduce
Do a fresh install using debian bulls-eye.
git clone https://github.com/getsentry/self-hosted.git sentry
cd sentry
./install.sh
go to webpage at port 9000
Expected Result
No issues reported after fresh install
Actual Result
Installed 3 times, same result. After a few seconds an issue is reported:
The issues continue to be reported growing the number of incidents.
The text was updated successfully, but these errors were encountered: