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

Fix spelling errors in comments and documentation (#7492)

Browse Source
This commit is contained in:
Josh Soref
2020-05-14 03:41:58 -04:00
committed by GitHub
parent c78045c13f
commit 2c56d6de81
134 changed files with 215 additions and 215 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
plugins/outputs/kinesis/README.md
View File

@@ -51,7 +51,7 @@ solution to scale out.
### use_random_partitionkey [DEPRECATED]
When true a random UUID will be generated and used as the partitionkey when sending data to Kinesis. This allows data to evenly spread across multiple shards in the stream. Due to using a random paritionKey there can be no guarantee of ordering when consuming the data off the shards.
When true a random UUID will be generated and used as the partitionkey when sending data to Kinesis. This allows data to evenly spread across multiple shards in the stream. Due to using a random partitionKey there can be no guarantee of ordering when consuming the data off the shards.
If true then the partitionkey option will be ignored.
### partition
@@ -70,7 +70,7 @@ All metrics will be mapped to the same shard which may limit throughput.
#### tag
This will take the value of the specified tag from each metric as the paritionKey.
This will take the value of the specified tag from each metric as the partitionKey.
If the tag is not found the `default` value will be used or `telegraf` if unspecified
#### measurement

2
plugins/outputs/kinesis/kinesis.go
View File

@@ -70,7 +70,7 @@ var sampleConfig = `
streamname = "StreamName"
## DEPRECATED: PartitionKey as used for sharding data.
partitionkey = "PartitionKey"
## DEPRECATED: If set the paritionKey will be a random UUID on every put.
## DEPRECATED: If set the partitionKey will be a random UUID on every put.
## This allows for scaling across multiple shards in a stream.
## This will cause issues with ordering.
use_random_partitionkey = false