Thomas Casteleyn
Thomas Casteleyn
@odain-cbd Why did You close this PR? And why did you remove the 3.2 branch?
@odain-cbd please reopen the PR
@jf-cbd I made it into an config option, this gives indeed more flexibility. Default stays `data/` dir for current and new customers.
@jf-cbd Archive_Tar has been updated to 1.6.0 which includes checks for correct writing to the file.. Do you expect anything else from me?
I have an additional use-case where the disk on `data/` is much slower than the disk of the system temporary directory. This increases the time to take a backup significantly.
Please verify with `--test`, but `docker_container_cpu_container_id` is not the name of a metric. (`docker_container_cpu` is and `container_id` is a field of that metric)
I would propose to use array syntax for selectors, that makes it similar to the existing [metric filtering](https://github.com/influxdata/telegraf/tree/master/config#metric-filtering) config. Ex: ```toml [[inputs.netstat]] [inputs.netstat.selector] app = ["frontend*", "backend"] drop = ["news-1"]...
I did and approved 😉
I'm just another guy from the community, just like You.. I was okay with the original spec indeed. However, I also agree with what @srebhan said. For me, both ways...
The more I read your use cases, the more I feel like this is already possible with telegraf (just other terminology) According to your latest scenario, you could have this:...