Thank you for the reply Hipska,
I spent some time attempting to use order
(and alias
) to “daisy chain” a _rate
metric into a basicstats
max
aggegator, but I could not get it to work. I tried using the same and different intervals and also using delay
but everytime when the basicstats
max
aggegator did operate it operated on the original metric and not the one produced by the previous basicstats
rate
aggegator. So I never get reads_rate_max
. If you have a working example then I would be interested in it.
When I run:
[[inputs.diskio]]
interval = "1s"
fieldpass = ["reads", "writes"]
[[aggregators.basicstats]]
order = 1
period = "2s"
drop_original = true
stats = ["rate"]
[[aggregators.basicstats]]
order = 2
interval = "10s"
drop_original = true
stats = ["max"]
[[outputs.file]]
files = ["stdout"
I get:
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=17 1614166828000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=53 1614166830000000000
diskio,host=X,name=nvme1n1p1 reads_max=18857956,writes_max=248039759 1614166830000000000
diskio,host=X,name=nvme1n1p1 writes_rate=53,reads_rate=0 1614166832000000000
diskio,host=X,name=nvme1n1p1 writes_rate=9,reads_rate=0 1614166834000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=4 1614166836000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=18 1614166838000000000
diskio,host=X,name=nvme1n1p1 writes_rate=104,reads_rate=0 1614166840000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=389 1614166842000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=389 1614166844000000000
diskio,host=X,name=nvme1n1p1 writes_rate=349,reads_rate=0 1614166846000000000
diskio,host=X,name=nvme1n1p1 writes_rate=333,reads_rate=0 1614166848000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=296 1614166850000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=444 1614166852000000000
diskio,host=X,name=nvme1n1p1 writes_rate=353,reads_rate=0 1614166854000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=364 1614166856000000000
diskio,host=X,name=nvme1n1p1 reads_rate=1,writes_rate=189 1614166858000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=0 1614166860000000000
diskio,host=X,name=nvme1n1p1 writes_max=248046577,reads_max=18857958 1614166860000000000
diskio,host=X,name=nvme1n1p1 writes_rate=23,reads_rate=0 1614166862000000000
diskio,host=X,name=nvme1n1p1 reads_rate=0,writes_rate=89 1614166864000000000
diskio,host=X,name=nvme1n1p1 writes_rate=3,reads_rate=0 1614166866000000000
Looking at:
Support ordering of processor plugins · influxdata/telegraf@b03c1d9 · GitHub
telegraf/config.go at 71a3a3cf20182c4537ce832bc7ca212870e7254f · influxdata/telegraf · GitHub and line 1181 and line 1137
it looks like order
is only used by Processors and not Aggregators, the docs do mention it is used with Processor Plugins:
telegraf/blob/master/docs/CONFIGURATION.md#processor-plugins
.) order: The order in which the processor(s) are executed. If this is not specified then processor execution order will be random.