-
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
LVM plugin #345
Comments
There is no LVM plugin, but that would be good to have |
Thanks for the info; I'll see whether I can add one. |
any idea what is current status? |
My logical volumes seem to work fine, can someone expand on the issue?
|
SELECT max("total") FROM "disk" WHERE "hostname" =~ /^$hostname$/ AND "device" = 'mapper/docker-8:1-50333733-000df53ce4e5fd58fccdbb7f7c991c5292d49dc2e214d3679f5419d9d6864e36' AND "fstype" = 'xfs' AND $timeFilter GROUP BY time($interval), "fstype" fill(null) my docker LVM size is 300 GB. but it is just showing just 10 GB. |
Can you paste the output of |
As per my knowledge df command wont give output of docker thin volume. docker info Server Version: 1.12.5 $ df -PH |
Okay, I guess the disk doesn't work for the same reason |
|
guys any progress or update on this? i ran into similar issue today. /var/log is mounted in our systems as LVM. i can see this volume from df -PH output( unlike docker storage where I can't see in df output) but still not able to see LVM's in device list df -t xfsFilesystem 1K-blocks Used Available Use% Mounted on df -PH I would be able to view only / file system or fstype is xfs but only root file system or device is only for sda1. Unable to view any info about other volumes any idea? is it a bug or intentional Srinivas Kotaru |
telegraf -config /etc/telegraf/telegraf.conf -input-filter disk -test
|
if you look at test command output, it is clearely giving info about only / or root file system. |
@danielnelson : Can you comment on this behaviour? |
Did you edit that output? I'm asking because I see |
I just removed the hostname which gives our identify. |
Okay, just double checking that there isn't an issue with the output. Can you paste you disk input config? |
[[inputs.cpu]] [[inputs.disk]] [[inputs.diskio]] [[inputs.kernel]] [[inputs.mem]] [[inputs.processes]] [[inputs.swap]] [[inputs.system]] [[inputs.net]] [[inputs.netstat]] [[inputs.docker]] [[inputs.procstat]] [[inputs.procstat]] |
Thanks, the thing I was most curious about was the path tags such as |
FYI in telegraf docker file, am not mounting /proc, /usr or /dev or /lib/modules from home file system. I am only exporting docker socket inside telegraf container and telegraf has read only access to docker socket. Since every container also its own /proc, /usr , /dev, /lib/modules, i didn't exported due to security and don't want telegraf container crash host since it running as a privileged container. |
The list of paths comes from |
from telegraf container. But am seeing correct mounts from host where container is running including LVM's cat /etc/mtabrootfs / rootfs rw 0 0 |
I guess the weird paths are the config files you are binding into the container.
Okay, that's just a distraction, we are trying to figure out why the It seems like you would need the host mtab file to be reachable for it to know about them. Honestly I'm not sure exactly how this is supposed to work, but the |
Most of the container specific agents ( datadog, sysdig etc) mount host file systems inside the container for easy identification between container file systems and host file systems https://stackoverflow.com/questions/33397382/host-monitoring-from-a-docker-container can we use telegraph is like that? i knew telegraf can be used as a container and standalone agent. If we using as a container but still want to monitor host where it is running, we need to export host file systems to containers and interpreted as host data |
I believe this is the subject of the discussion on the issue I linked, I would try following these steps #1544 (comment) |
Just to add my particular situation, I'm wanting to monitoring LVM volume group usage for an OpenStack CInder server/node. Since none of the logical volumes are even mounted on the Cinder node itself, I don't have a way to look at the space used via telegraf directly (as far as I am aware). |
Hi all I'm much interesting in such volume. I'm using Docker CE on CentOS 7 using the devicemapper (aka LVM) storage backend. What Docker does is use a thin provisioning LV which is never mounted (so it is not monitored by the I'm not too much interested in monitoring the file size of each block devices created by Docker for each container, because I'm using volumes for where data are written, this is not too interesting. BUT I am very interested in monitoring the Docker dedicated thin provision LV (which I can check with So it would be nice if the |
Is there a LVM plugin available? The disk plugin does not seem to be able to figure out the sizes of LVM volumes correctly.
I am using version 0.2.0
The text was updated successfully, but these errors were encountered: