Can you please add this based on the DWH docs?

(In reply to Emma Heftman from comment #0)
> The following plugins have only very limited documentation on the web:
> 
> collectd.statsd.host_storage

> collectd.statsd.vm_balloon_cur
The current amount of memory available to the guest (in KiB)

> collectd.statsd.vm_balloon_max
The maximum amount of memory available to the guest (in KiB)

> collectd.statsd.vm_balloon_min
The minimum amount of memory guaranteed to the guest (in KiB)

> collectd.statsd.vm_balloon_target
The amount of memory requested (in KiB)

> collectd.statsd.vm_cpu_sys
Ratio of CPU time spent by qemu on other than guest time

> collectd.statsd.vm_cpu_usage
Total cpu usage since VM start in ns

> collectd.statsd.vm_cpu_user
Ratio of CPU time spent by the guest VM

> collectd.statsd.vm_disk_apparent_size
The size of the disk (in bytes)

> collectd.statsd.vm_disk_flush_latency
The virtual disk flush latency measured in seconds.

> collectd.statsd.vm_disk_read_bytes
Read rate to disk in bytes per second.

> collectd.statsd.vm_disk_read_latency
The virtual disk read latency measured in seconds.

> collectd.statsd.vm_disk_read_ops
Read operations since VM start

> collectd.statsd.vm_disk_read_rate
The read activity in bytes per second

> collectd.statsd.vm_disk_true_size
The amount of underlying storage allocated (in bytes)

> collectd.statsd.vm_disk_write_bytes
Write rate to disk in bytes per second.

> collectd.statsd.vm_disk_write_latency
The virtual disk write latency measured in seconds.

> collectd.statsd.vm_disk_write_ops
Write operations since VM start 

> collectd.statsd.vm_disk_write_rate
The write activity in bytes per second

> collectd.statsd.vm_nic_rx_bytes
The number of incoming bytes in total

> collectd.statsd.vm_nic_rx_dropped
The number of incoming packets that have been dropped

> collectd.statsd.vm_nic_rx_errors
The number of incoming packets that have contained errors

> collectd.statsd.vm_nic_speed
The interface speed (in Megabits/s)

> collectd.statsd.vm_nic_tx_bytes
The number of outgoing bytes in total

> collectd.statsd.vm_nic_tx_dropped
The number of outgoing packets that have been dropped

> collectd.statsd.vm_nic_tx_errors
The number of outgoing packets that have contained errors

Can you please explain collectd.statsd.host_storage metric? What are the units, What is the description.

host storage key contains the storageDomain "delay" and "last check" values.  the time costs for writing to storage domain and when it occurred

(In reply to Yaniv Bronhaim from comment #4)
> host storage key contains the storageDomain "delay" and "last check" values.
> the time costs for writing to storage domain and when it occurred

Hi Yaniv/Shirly
You have described two values here, the delay and when it occurred, however, we only have one metric - collectd.statsd.host_storage, so could you tell me which value is collected?
Thanks!

(In reply to Emma Heftman from comment #5)
> (In reply to Yaniv Bronhaim from comment #4)
> > host storage key contains the storageDomain "delay" and "last check" values.
> > the time costs for writing to storage domain and when it occurred
> 
> Hi Yaniv/Shirly
> You have described two values here, the delay and when it occurred, however,
> we only have one metric - collectd.statsd.host_storage, so could you tell me
> which value is collected?
> Thanks!

Information from Nir Sofer:
We need both. The delay is the time to read from storage. We use this value to
display warnings in engine when the delay is too long (more than 5 seconds).

lastcheck .... this is not the time of the last check, but the time
since the last check.

If the last check was at 12:59:00, and I check the status at 12:59:32
lastCheck will be 32.00 seconds.

High lastCheck value mean that the storage monitor is stuck, or in other
words, storage is not responsive.

Shirly, which of these values do you display?

Accepting into 4.2.5 program.

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Shirly, I didn't see you respond to https://bugzilla.redhat.com/show_bug.cgi?id=1528219#c8 so I'm reassigning this to you to approve the descriptions we wrote for statsd for virt.