-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker input plugin #14319
Comments
Good to see that there is demand for the storage objects part of the docker input plugin. The pull request that actually adds the functionality (#13894) is scheduled to be added in v1.29.0 (https://github.com/influxdata/telegraf/milestone/94?closed=1). Would you be interested in testing the Telegraf nightly version? You can download it at: https://www.influxdata.com/downloads/ |
Hello, Thank you for letting me know, I didn't know it was not implemented yet since the documentation is available. Yes, I would be interested. I installed it and so far it works just fine, for all types of docker objects: container, image, and volume. |
@clement-deltel so your issue was using a not-yet-released feature? Everything works and we can close the issue? |
Yes, this is exactly what happened. You can close this issue. |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.28.5, Ubuntu 22.04, Docker version 24.0.7, build afdd53b
Docker
No response
Steps to reproduce
If the storage_objects option is commented out, it works just fine. If I uncomment it, Telegraf crashes and refuses to start. I tried the following, without success
Expected behavior
Since Telegraf supports Docker metrics, enabling the option for Docker disk_usage should work just fine and rebooting Telegraf should not fail.
Actual behavior
As soon as I enable the "storage_objects" option and reboot Telegraf to apply the changes, it fails and Telegraf refuses to boot. I don't have much more from the service apart from the fact that it is not booting.
Additional info
No response
The text was updated successfully, but these errors were encountered: