-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
Vector support #431
Comments
Further testing shows it works with non-TLS MQTT. I'll see if there's a limitation with MQTTS. Where does Emitter store the cert for testing with https://vector.dev/docs/reference/configuration/sinks/mqtt/#tls ? |
Never mind, I didn't install OpenSSL since "Vector implements cryptography and secure communication using the OpenSSL library. In particular, the official Vector binaries are statically linked against OpenSSL version 3.3.2 and do not use any OpenSSL library installed on the running system." [source] but by not having it installed my system didn't have the trusted certificate paths configured so Vector didn't have the Let's Encrypt cert loaded. Installing OpenSSL solved the issue. |
After a reboot it fails to connect. Will investigate further. Since Vector uses https://github.com/bytebeamio/rumqtt under the hood, I'll start there. Ref: #388 |
Findings summary: vectordotdev/vector#21374 (comment) Since the request to upgrade Emitter to MQTT protocol 5 was marked |
Vector is a popular open source observability platform and supports MQTT but when it tries to connect to Emitter it throws
ERROR vector::internal_events::mqtt: MQTT connection error. error=I/O: connection closed by peer error_code="mqtt_connection_error" error_type="writer_failed" stage="sending" internal_log_rate_limit=true
Thoughts?
The text was updated successfully, but these errors were encountered: