Joshua Powers

next step: figure out the best way to collect this data, ensure it is not already collected by some other plugin, and implement it.

I consider BurntSushi/toml the canonical source, this does appear to work and it is valid TOML syntax: ```go package main import ( "fmt" "log" "github.com/BurntSushi/toml" ) var tomlData = `...

next steps: see how it would be possible to add `label_include` and `label_exclude` config options to `kube_inventory`

I have an Ubuntu 22.04 system which has podman 3.4.4, and that seems to work: ```s ubuntu@nuci5a:~/telegraf-1.23.3/usr/bin$ ls -l /var/run/podman/podman.sock srw-rw---- 1 root root 0 Aug 4 14:06 /var/run/podman/podman.sock ubuntu@nuci5a:~/telegraf-1.23.3/usr/bin$...

@tiny6996 what does `sudo podman info | grep sock` report? For me it shows as `/run/podman/podman.sock`. I went to start looking at this again and re-installed podman ([podman info](https://paste.ubuntu.com/p/xkZNSgH3Sb/)) and...

next steps: look into adding a config option that will let users set this regex

Hi, ``` partial write: field type conflict: input field "interface_up" on measurement "ethtool" is type integer, already exists as type boolean dropped=1 ``` This means that Telegraf already wrote the...

Discussed and next steps include: 1) see how many telegraf specific metric names are created 2) evaluate the possible future impact 3) either special case the above if small enough...

next steps: review the now closed PR #9875 and see if it resolves the issue

Hi, I see this is a draft, but I was curious: have you thought about using the `exec` or even `file` inputs? You can put whatever mock metrics you want...