使用oVirt收集磁盘使用统计信息

Question

我使用REST来使用oVirt REST收集虚拟磁盘的统计信息，并得到了以下响应，

https://1.1.1.1/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996/statistics/

对这个API的响应，

{
  "statistic": [{
    "kind": "gauge",
    "type": "decimal",
    "unit": "bytes_per_second",
    "values": {
      "value": [{
        "datum": 0
      }]
    },
    "disk": {
      "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996",
      "id": "b14da816-37e3-46d7-8617-2e42e52db996"
    },
    "name": "data.current.read",
    "description": "Read data rate",
    "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
    "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
  }, {
    "kind": "gauge",
    "type": "decimal",
    "unit": "bytes_per_second",
    "values": {
      "value": [{
        "datum": 0
      }]
    },
    "disk": {
      "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996",
      "id": "b14da816-37e3-46d7-8617-2e42e52db996"
    },
    "name": "data.current.write",
    "description": "Write data rate",
    "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
    "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
  }, {
    "kind": "gauge",
    "type": "decimal",
    "unit": "seconds",
    "values": {
      "value": [{
        "datum": 0
      }]
    },
    "disk": {
      "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996",
      "id": "b14da816-37e3-46d7-8617-2e42e52db996"
    },
    "name": "disk.read.latency",
    "description": "Read latency",
    "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996/statistics/3a7b3f72-d035-3bb9-b196-e86a4eb34993",
    "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
  }, {
    "kind": "gauge",
    "type": "decimal",
    "unit": "seconds",
    "values": {
      "value": [{
        "datum": 0
      }]
    },
    "disk": {
      "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996",
      "id": "b14da816-37e3-46d7-8617-2e42e52db996"
    },
    "name": "disk.write.latency",
    "description": "Write latency",
    "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996/statistics/b1e75c7b-cea4-37d2-8459-f7d68efc69a3",
    "id": "b1e75c7b-cea4-37d2-8459-f7d68efc69a3"
  }, {
    "kind": "gauge",
    "type": "decimal",
    "unit": "seconds",
    "values": {
      "value": [{
        "datum": 0
      }]
    },
    "disk": {
      "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996",
      "id": "b14da816-37e3-46d7-8617-2e42e52db996"
    },
    "name": "disk.flush.latency",
    "description": "Flush latency",
    "href": "/ovirt-engine/api/disks/b14da816-37e3-46d7-8617-2e42e52db996/statistics/9c17ad7b-9ef1-3e8d-ad0a-ff8bee3925f0",
    "id": "9c17ad7b-9ef1-3e8d-ad0a-ff8bee3925f0"
  }]
}

因此，根据我的理解，它能够检索5个统计数据(即读写带宽、读写和刷新延迟)。

我的问题是，是否可能获得虚拟磁盘/ VM的读/写IOPS？

谢谢,

哈里

Answer 1

https://bugzilla.redhat.com/show_bug.cgi?id=876697似乎回答了这个问题。它指出，对于度量版本3.0.7：

每个磁盘从virt插件度量到每个vm的收集器度量，对于这个RFE来说就足够了。collectd.virt.disk_ops.read collectd.virt.disk_ops.write这些度量应该允许用户根据这个RFE中的要求快速/容易地识别那些使用高I/O的VM。磁盘名保存为collectd.type_instance。VM名称保存为collectd.plugin_instance。至于能够聚合每个VM的存储IOPS，这在现阶段是不可能的，因为磁盘名称不是驱动器名称--这是libvirt所猜测的，因此不能跨vms进行聚合。用户可以登录到vm，以便检查驱动器名。

和

聚集部分将在单独的BZ中求解。在ovirt-engine中验证-度量-1.1.3.3-1.el7ev.noarch.noarch-1.1.3.3-1.el7