Hello Proxmox community!
I'm working on a monitoring script that collects filesystem information from multiple VMs using the agent/get-fsinfo API endpoint. However, I've hit a major roadblock:
The Problem:
When I call GET /api2/json/nodes/{node}/qemu/{vmid}/agent/get-fsinfo, the response contains detailed filesystem data but doesn't include the VM ID in the response body. This makes it impossible to correlate the data back to the specific VM when processing results from multiple VMs.
Even More Critical Issue:
This limitation makes it impossible to properly combine data from agent/get-fsinfo with other API endpoints like:
/api2/json/nodes/{{node}}/qemu/{{vmid}}/status/current
Example scenario:
My question to the community:
{
"vmid": 100,
"data": [
{
"name": "sda1",
"type": "ext4",
"size": 528449536,
"mountpoint": "/"
}
]
}
Has anyone else faced this issue? How did you solve it? Would this be a useful feature request for the Proxmox team?
I'm working on a monitoring script that collects filesystem information from multiple VMs using the agent/get-fsinfo API endpoint. However, I've hit a major roadblock:
The Problem:
When I call GET /api2/json/nodes/{node}/qemu/{vmid}/agent/get-fsinfo, the response contains detailed filesystem data but doesn't include the VM ID in the response body. This makes it impossible to correlate the data back to the specific VM when processing results from multiple VMs.
Even More Critical Issue:
This limitation makes it impossible to properly combine data from agent/get-fsinfo with other API endpoints like:
/api2/json/nodes/{{node}}/qemu/{{vmid}}/status/current
Example scenario:
- I have 30 VMs running across multiple nodes
- I loop through all of them calling get-fsinfo and status/current
- The get-fsinfo responses contain no VM identifier
- The status/current responses do contain VM ID
- I cannot reliably merge this data because there's no common identifier in the get-fsinforesponse
My question to the community:
- Is this by design? Am I missing something obvious?
- How are others solving this problem in their scripts?
- Would it make sense to have the VM ID included in the response?
- Any clever workarounds you've implemented?
{
"vmid": 100,
"data": [
{
"name": "sda1",
"type": "ext4",
"size": 528449536,
"mountpoint": "/"
}
]
}
Has anyone else faced this issue? How did you solve it? Would this be a useful feature request for the Proxmox team?