Damien PIQUET
Damien PIQUET
Hi, All you have to do on the Proxmox side is configuring a readonly access to the api (see http://pve-monitor.scriptutils.com/english/create-a-pve-readonly-user/ ) So all requirements installation has to be done on...
From the api, lxc or openvz doesn't matter, they can be monitored the same way. Maybe a run with debug enabled could help
Add something like this to pve-monitor's configuration file qemu monitoring { mem 80 90 cpu 80 95 disk 80 90 }
You can use pools to group your vms inside PVE. Then monitor this pool using the pool keyword like this pool Sample { mem 98 100 cpu 90 95 disk...
I was about to ask you the version you were using. If this is an exact copy/paste, you have a space between -- and conf which should be --conf
the pool argument just tells pve-monitor to use pool defined ressources. You have to specify --qemu, --storage or --openvz to get results. pve-monitor does not to monitor if vms are...
Hi, I would need more info to help you. Options used? Configuration file ?
Hi, Thanks for this well detailed bug report. I will need to install a test setup with that configuration so i can reproduce the bug and fix it. I'm quite...
Well I don't think it's the case. Currently the code dies at argument parsing. Of course it's not excluded that i'll have problems with the rest of the code but...
Bonjour, Je n'ai pas testé le plugin avec shinken ou thruk. Pour le disque renvoyant toujours 0 je ne vois pas d'ou cela peut venir. Quel est le taux d'occupation...