Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Is it present and inaccessible in the container? If it shows up in df there, what are the specific symptoms of telegraf not being able to use it? Commented Jun 5 at 16:57
  • @grawity The output of Telegraf to stdout that should display the metrics does not show the disk data for that drive. Directories on the mounted drive are accessible from inside the container. It is as if the drive is still mounted (but I can see from the journalctl logs on the host that it was in fact auto-unmounted) Commented Jun 5 at 16:59
  • Does it show the metrics at the very beginning when the container is started, though? I see your telegraf config .../TIG_backups does not actually match the bind mount .../TIG_backups/telegraf_backups that is visible to the container, so effectively it's told to monitor a subdirectory of / and not any NFS mount, no? Commented Jun 5 at 17:12