dom
/
telegraf
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Clarify use of multiple mqtt broker servers

This commit is contained in:
Daniel Nelson 2020-06-04 14:43:05 -07:00
parent 36316ee8f2
commit 6f931c9834
No known key found for this signature in database
GPG Key ID: CAAD59C9444F6155
2 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
plugins/inputs/mqtt_consumer/README.md
View File

@ -7,8 +7,11 @@ and creates metrics using one of the supported [input data formats][].
```toml
[[inputs.mqtt_consumer]]
## MQTT broker URLs to be used. The format should be scheme://host:port,
## schema can be tcp, ssl, or ws.
## Broker URLs for the MQTT server or cluster. To connect to multiple
## clusters or standalone servers, use a seperate plugin instance.
## example: servers = ["tcp://localhost:1883"]
## servers = ["ssl://localhost:1883"]
## servers = ["ws://localhost:1883"]
servers = ["tcp://127.0.0.1:1883"]
## Topics that will be subscribed to.

7
plugins/inputs/mqtt_consumer/mqtt_consumer.go
View File

@ -76,8 +76,11 @@ type MQTTConsumer struct {
}
var sampleConfig = `
## MQTT broker URLs to be used. The format should be scheme://host:port,
## schema can be tcp, ssl, or ws.
## Broker URLs for the MQTT server or cluster. To connect to multiple
## clusters or standalone servers, use a seperate plugin instance.
## example: servers = ["tcp://localhost:1883"]
## servers = ["ssl://localhost:1883"]
## servers = ["ws://localhost:1883"]
servers = ["tcp://127.0.0.1:1883"]
## Topics that will be subscribed to.