Telegraf MSK kafka input plugin

[Anaisdg]

Hello @Ajinkya_patil,
I’m not super familiar with the kafka plugin:
Here are similar issues it the community though:

[telegraf] Error running agent: starting input inputs.kafka_consumer: create consumer: kafka: client has run out of available brokers to talk to: dial tcp: address 10.166.139.204:9092,10.166.139.205:9092,10.166.139.206:9092: too many colons in address

[微信截图_20230731105820] this is my brokers,why is this so?

Telegraf ..could not initialize output kafka: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)

Execute telegraf -config ~/telegraf.conf -test 2021-02-17T19:40:40Z I! Starting Telegraf 1.17.2 2021-02-17T19:40:40Z D! [agent] Initializing plugins 2021-02-17T19:40:40Z W! [kafka] enable_tls is deprecated, and the setting does nothing, you can safely remove it from the config 2021-02-17T19:40:40Z D! [sarama] Initializing new client 2021-02-17T19:40:40Z D! [sarama] client/metadata fetching metadata for all topics from broker 127.0.0.1:9092 2021-02-17T19:40:40Z D! [sarama] Connected to bro…

Continous restart in Telegraf when an output (kafka) is not reachable

Continous restart in Telegraf when an output (kafka or elasticsearch or any ) is not reachable, the servicekeeps restarting over and over. It is right, one of the outputs configured is down, in this case is Kafka, but is this a reason for telegraf to restart so many times? Telegraf log 2019-04-15T15:06:13Z E! Failed to connect to output kafka, retrying in 15s, error was ‘kafka: client has run out of available brokers to talk to (Is your cluster reachable?)’ 2019-04-15T15:06:28Z E! kafka: cli…

Let me know if one of those solutions helps