> What (range of) latency will this introduce to Telegraf metrics displayed in
> Grafana?
Instead of having a collection every <interval> (10 seconds by default), it will get a collection between the <interval+collection_jitter> *for each plugin*. So a same instance of telegraf could gather bcache metrics at, say, 11 seconds, and the procstat one at 13 seconds.
The precision of the jitter is the nanosecond though [0][1]
I'll try to gather a snapshot of a graph with "before/after" the change on a compute node and all instances' telegraf.
Changing just on a compute node hasn't been conclusive.
> What (range of) latency will this introduce to Telegraf metrics displayed in
> Grafana?
Instead of having a collection every <interval> (10 seconds by default), it will get a collection between the <interval+ collection_ jitter> *for each plugin*. So a same instance of telegraf could gather bcache metrics at, say, 11 seconds, and the procstat one at 13 seconds.
The precision of the jitter is the nanosecond though [0][1]
[0]: https:/ /github. com/influxdata/ telegraf/ blob/v1. 16.2/agent/ tick.go# L35 /golang. org/pkg/ time/#Duration
[1]: https:/
I'll try to gather a snapshot of a graph with "before/after" the change on a compute node and all instances' telegraf.
Changing just on a compute node hasn't been conclusive.