Thx daniel for the quick support.
We updated telegraf and restarted with the same configuration.
No success ...
> 2019-09-02T07:52:49Z D! [sarama] client/metadata fetching metadata for all topics from broker *.servicebus.windows.net:9093
2019-09-02T07:52:49Z D! [sarama] Failed to read SASL handshake header : EOF
2019-09-02T07:52:49Z D! [sarama] Error while performing SASL handshake *.servicebus.windows.net:9093
2019-09-02T07:52:49Z D! [sarama] Closed connection to broker *.servicebus.windows.net:9093
On using kafka port 9092 I get a different log.
> 2019-09-02T07:38:19Z D! [sarama] client/metadata fetching metadata for all topics from broker *.servicebus.windows.net:9092
2019-09-02T07:38:49Z D! [sarama] Failed to connect to broker *.servicebus.windows.net:9092: dial tcp 13.69.64.0:9092: i/o timeout
2019-09-02T07:38:49Z D! [sarama] client/metadata got error from broker -1 while fetching metadata: dial tcp 13.69.64.0:9092: i/o timeout
With this it looks like the port 9092 works better than 9093. Looks like SASL authenication works. However the Microsoft documentation [Data streaming with Event Hubs using the Kafka protocol](
https://docs.microsoft.com/de-de/azure/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs) uses port 9093.
Any ideas how to proceed?
* Is there a way to get more log on sarama?
* The different ports 9092 and 9093 confuses me.
Thx for help ....
Bruno
---