-
|
We removed TLS on the MQTT side to make it simpler. But it is not working correctly
Confluent Cloud IoT Ingest and Control solution docs
name: public
telemetry:
metrics:
- stream.opens.sent
- stream.closes.sent
- stream.errors.sent
- stream.errors.received
- stream.closes.received
- stream.opens.received
exporters:
stdout:
type: stdout
bindings:
tcp_server:
type: tcp
kind: server
telemetry:
metrics:
- stream.*
options:
host: 0.0.0.0
port: 1883
exit: mqtt_server
mqtt_server:
type: mqtt
kind: server
telemetry:
metrics:
- stream.*
options:
versions:
- v5
- v3.1.1
exit: mqtt_kafka_mapping
mqtt_kafka_mapping:
type: mqtt-kafka
kind: proxy
telemetry:
metrics:
- stream.*
options:
topics:
sessions: iot-zilla-mqtt-sessions
messages: iot-zilla-mqtt-messages
retained: iot-zilla-mqtt-retained
clients:
- spBv1.0/PAULv0/+/{identity}/#
exit: kafka_cache_client
kafka_cache_client:
type: kafka
kind: cache_client
telemetry:
metrics:
- stream.*
exit: kafka_cache_server
kafka_cache_server:
type: kafka
kind: cache_server
telemetry:
metrics:
- stream.*
options:
bootstrap:
- iot-zilla-mqtt-messages
- iot-zilla-mqtt-retained
exit: kafka_client
kafka_client:
type: kafka
kind: client
options:
servers:
- ${{aws.secrets.arn:aws:secretsmanager:*:secret:*#bootstrap_server}}
sasl:
mechanism: plain
username: "${{aws.secrets.arn:aws:secretsmanager:*:secret:*#api_key}}"
password: "${{aws.secrets.arn:aws:secretsmanager:*:secret:*#api_secret}}"
telemetry:
metrics:
- stream.*
exit: tls_client
tls_client:
type: tls
kind: client
vault: secure
telemetry:
metrics:
- stream.*
exit: tcp_client
tcp_client:
type: tcp
kind: client
telemetry:
metrics:
- stream.* |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
@yveskurz we have found and fixed the issue reported with MQTT Explorer and verified Confluent Cloud connectivity as well with the latest Zilla release. Note: An updated Zilla Plus release is in flight including the fix. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the informations @yveskurz . I managed to reproduce the issue using my local setup with MQTT Explorer. |
Beta Was this translation helpful? Give feedback.
-
|
These are the topic configuration on confluent cloud Further, I've set the client id to the topic I'm posting message to. So the clientID is P01010151iae4N5, topic I'm publishing to is spBv1.0/PAULv0/DDATA/P01010151iae4N5/P12344 It sometimes, but very rarely, the message get's produced to the messages topic, but it takes a very long time that the mqtt message appears on the Kafka topic (like 10s of seconds). Also as @bmaidics suggested, I've removed the clients option from mqtt-kafka completely and restarted zilla. The result was exactly the same. |
Beta Was this translation helpful? Give feedback.
-
|
Also I can see based on your config you have clients mqtt-kafka option: |
Beta Was this translation helpful? Give feedback.
-
|
Just to make sure: when you created the topics for the sessions (iot-zilla-mqtt-sessions), did you created it as compact? Also the retained topic (iot-zilla-mqtt-retained) should be compact. |
Beta Was this translation helpful? Give feedback.
@yveskurz we have found and fixed the issue reported with MQTT Explorer and verified Confluent Cloud connectivity as well with the latest Zilla release.
#1189
Note: An updated Zilla Plus release is in flight including the fix.