Hello,
I love the vsphere module that was added to metricbeat, however, there aren't enough different kinds of metrics being pulled for me to move away from my current metric collection methods. Would it be possible to include metrics that for example Zabbix can pull by default? This would be huge for me in terms of moving everything over to metricbeat for data collection.
I.E:
Where hv is hyper-visor metrics and vm is virtual-machine metrics_
vmware.hv.cluster.name
vmware.hv.cpu.usage
vmware.hv.datacenter.name
vmware.hv.fullname[
vmware.hv.hw.cpu.freq
vmware.hv.hw.cpu.model
vmware.hv.hw.cpu.num
vmware.hv.hw.cpu.threads
vmware.hv.hw.memory
vmware.hv.hw.model
vmware.hv.hw.uuid
vmware.hv.hw.vendor
vmware.hv.memory.size.ballooned
vmware.hv.memory.used
vmware.hv.network.in
vmware.hv.network.out
vmware.hv.sensor.health.state
vmware.hv.status
vmware.hv.uptime
vmware.hv.version
vmware.hv.vm.num
vmware.hv.datastore.read
vmware.hv.datastore.write
vmware.hv.datastore.size
vmware.hv.datastore.size
vmware.hv.cluster.name
vmware.hv.cpu.usage
vmware.hv.datacenter.name
vmware.hv.fullname
vmware.hv.hw.cpu.freq
vmware.hv.hw.cpu.model
vmware.hv.hw.cpu.num
vmware.hv.hw.cpu.threads
vmware.hv.hw.memory
vmware.hv.hw.model
vmware.hv.hw.uuid
vmware.hv.hw.vendor
vmware.hv.memory.size.ballooned
vmware.hv.memory.used
vmware.hv.network.in
vmware.hv.network.out
vmware.hv.sensor.health.state
vmware.hv.status
vmware.hv.uptime
vmware.hv.version
vmware.hv.vm.num
vmware.vm.cluster.name
vmware.vm.cpu.num
vmware.vm.cpu.ready
vmware.vm.cpu.usage
vmware.vm.datacenter.name
vmware.vm.hv.name
vmware.vm.memory.size.ballooned
vmware.vm.memory.size.compressed
vmware.vm.memory.size.private
vmware.vm.memory.size.shared
vmware.vm.memory.size.swapped
vmware.vm.memory.size.usage.guest
vmware.vm.memory.size.usage.host
vmware.vm.memory.size
vmware.vm.powerstate
vmware.vm.storage.committed
vmware.vm.storage.uncommitted
vmware.vm.storage.unshared
vmware.vm.uptime
vmware.cluster.status
Hello,
I love the vsphere module that was added to metricbeat, however, there aren't enough different kinds of metrics being pulled for me to move away from my current metric collection methods. Would it be possible to include metrics that for example Zabbix can pull by default? This would be huge for me in terms of moving everything over to metricbeat for data collection.
I.E:
Where hv is hyper-visor metrics and vm is virtual-machine metrics_
vmware.hv.cluster.name
vmware.hv.cpu.usage
vmware.hv.datacenter.name
vmware.hv.fullname[
vmware.hv.hw.cpu.freq
vmware.hv.hw.cpu.model
vmware.hv.hw.cpu.num
vmware.hv.hw.cpu.threads
vmware.hv.hw.memory
vmware.hv.hw.model
vmware.hv.hw.uuid
vmware.hv.hw.vendor
vmware.hv.memory.size.ballooned
vmware.hv.memory.used
vmware.hv.network.in
vmware.hv.network.out
vmware.hv.sensor.health.state
vmware.hv.status
vmware.hv.uptime
vmware.hv.version
vmware.hv.vm.num
vmware.hv.datastore.read
vmware.hv.datastore.write
vmware.hv.datastore.size
vmware.hv.datastore.size
vmware.hv.cluster.name
vmware.hv.cpu.usage
vmware.hv.datacenter.name
vmware.hv.fullname
vmware.hv.hw.cpu.freq
vmware.hv.hw.cpu.model
vmware.hv.hw.cpu.num
vmware.hv.hw.cpu.threads
vmware.hv.hw.memory
vmware.hv.hw.model
vmware.hv.hw.uuid
vmware.hv.hw.vendor
vmware.hv.memory.size.ballooned
vmware.hv.memory.used
vmware.hv.network.in
vmware.hv.network.out
vmware.hv.sensor.health.state
vmware.hv.status
vmware.hv.uptime
vmware.hv.version
vmware.hv.vm.num
vmware.vm.cluster.name
vmware.vm.cpu.num
vmware.vm.cpu.ready
vmware.vm.cpu.usage
vmware.vm.datacenter.name
vmware.vm.hv.name
vmware.vm.memory.size.ballooned
vmware.vm.memory.size.compressed
vmware.vm.memory.size.private
vmware.vm.memory.size.shared
vmware.vm.memory.size.swapped
vmware.vm.memory.size.usage.guest
vmware.vm.memory.size.usage.host
vmware.vm.memory.size
vmware.vm.powerstate
vmware.vm.storage.committed
vmware.vm.storage.uncommitted
vmware.vm.storage.unshared
vmware.vm.uptime
vmware.cluster.status