You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/virtual_machines.rst
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1327,6 +1327,42 @@ CloudStack follows the below sequence of operations to provide GPU/vGPU support
1327
1327
GPU resources are released automatically when you stop a VM. Once the destroy VM is successful, CloudStack will make a resource call to the host to get the remaining GPU capacity in the card and update the database accordingly.
1328
1328
1329
1329
1330
+
Virtual Machine Metrics
1331
+
=======================
1332
+
1333
+
VM statistics are collected on a regular interval (defined by global
1334
+
setting vm.stats.interval with a default of 60000 milliseconds).
1335
+
VM statistics include include compute, storage and network statistics.
1336
+
1337
+
VM statistics are stored in the database as historical data for a desired time period. These historical statistics then can be retrieved using listVirtualMachinesUsageHistory API. For system VMs, the same historical statistics can be retrieved using listSystemVmsUsageHistory API
1338
+
1339
+
VM statistics retention time in the database is controlled by the global configuration - `vm.stats.max.retention.time`. Default value is 720 minutes, i.e., 12 hours. Another global configuration that affects virtual machine statistics is:
1340
+
1341
+
- `vm.stats.user.vm.only` - When set to 'false' stats for system VMs will be collected otherwise stats collection will be done only for user VMs.
1342
+
1343
+
In the UI, historical VM statistics are shown in the Metrics tab in an individual VM view, as shown in the image below.
1344
+
1345
+
|vm-metrics-ui.png|
1346
+
1347
+
1348
+
VM Disk Metrics
1349
+
---------------
1350
+
1351
+
Similar to VM statistics, VM disk statistics (disk stats) can also be collected on a regular interval (defined by global setting vm.disk.stats.interval with a default value of 0 seconds which disables disk stats collection). Disk stats are collected in form of diskiopstotal, diskioread, diskiowrite, diskkbsread and diskkbswrite.
1352
+
1353
+
VM disk statistics can also be made to store in the database and the historical statistics can be retrieved using listVolumesUsageHistory API.
1354
+
1355
+
VM disk statistics retention in the database is controlled by the global configuration - `vm.disk.stats.retention.enabled`. Default value is false, i.e., retention of VM disk statistics is disabled. Other global configurations that affects virtual machine disk statistics are:
1356
+
1357
+
- `vm.disk.stats.interval.min` - Minimal interval (in seconds) to report vm disk statistics. If vm.disk.stats.interval is smaller than this, use this to report vm disk statistics.
1358
+
1359
+
- `vm.disk.stats.max.retention.time` - The maximum time (in minutes) for keeping disk stats records in the database. The disk stats cleanup process will be disabled if this is set to 0 or less than 0.
1360
+
1361
+
VM disk statistics are shown in the Metrics tab in an individual volume view, as shown in the image below.
0 commit comments