-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
snuba erroring out with SASL connection to Kafka not being supported only PLAIN? #3383
Comments
Alena86
changed the title
snuba erroring out with SASL connection to Kafka
snuba erroring out with SASL connection to Kafka not being supported only PLAIN?
Oct 14, 2024
It's not supported, see here getsentry/snuba#6358 (comment) I'm not an employee, so I suggest creating another issue at the snuba repo. |
Got ya.. |
getsantry
bot
added
Waiting for: Product Owner
and removed
Waiting for: Community
labels
Oct 15, 2024
getsantry
bot
moved this from Waiting for: Community
to Waiting for: Product Owner
in GitHub Issues with 👀 3
Oct 15, 2024
Yes that's the one! |
Duplicate of getsentry/snuba#6441. Let's keep only one issue open. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Self-Hosted Version
24.9.0
CPU Architecture
x86_64
Docker Version
26.0.2 build 3c863ff
Docker Compose Version
v2.26.1
Steps to Reproduce
in the docker compose file:
DEFAULT_BROKERS: "kafka:9092"
to have KAFKA settings:Tried even setting DEFAULT_BROKERS to be SASL_PLAINTEXT://kafka.ourdomain.com:9094 as we use 9094 port instead of 9092... even tried for the sake of it setting 9092 but the same error which would be the SASL not being supported in snuba container...
Expected Result
Expected result was to connect Sentry setup to our instance of Kafka and be able to open Sentry and login.
Actual Result
installation goes through, but once we run docker compose up, we are getting bunch of errors from snuba about not being able to connect to Kafka:
it comes from almost all the snuba components the same error.
Is snuba image really not supporting Kafka SASL?
And I thought snuba is supposed to be connecting only to clickhouse? Why does it even need kafka configuration?
Thanks for the help!
Event ID
No response
The text was updated successfully, but these errors were encountered: