[ovirt-users] Re: Disk Statistics API in oVirt

[Hari Prasanth Loganathan]

Sure Andrej. Thanks.

I sent another mail for API issues :Mail Subject: API for attaching the ISO
image and virtual floppy disk to the VMCould you please check this also.


On Tue, Jul 31, 2018 at 4:15 PM, Andrej Krejcir  wrote:

> Hi,
>
> Looking at the code, the disk statistics are only updated when the VM is
> running.
> It looks like a bug. Could you open a Bugzilla ticket, so we can properly
> fix it?
>
> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> Set the component to: Backend.Core
> And oVirt Team to: Virt
>
>
> Regards,
> Andrej
>
> On Mon, 30 Jul 2018 at 20:01, Hari Prasanth Loganathan  msystechnologies.com> wrote:
>
>> Thanks Greg, please let me know this.
>>
>>
>> On Mon, 30 Jul 2018 at 11:29 PM, Greg Sheremeta 
>> wrote:
>>
>>> Sorry for the delay. adding some others that may know.
>>>
>>> On Sun, Jul 29, 2018 at 11:02 PM Hari Prasanth Loganathan <
>>> hariprasant...@msystechnologies.com> wrote:
>>>
 Hi Guys,

 Any update on this, please?

 Thanks,
 Hari

 On Fri, Jul 27, 2018 at 5:52 AM, Greg Sheremeta 
 wrote:

> + @Tomas Jelinek  do you know this one?
>
> On Wed, Jul 18, 2018 at 1:57 AM Hari Prasanth Loganathan <
> hariprasant...@msystechnologies.com> wrote:
>
>> Hi Karli,
>>
>> Sorry for the confusion, Initially I thought it is an issue from our
>> side so posted like 'ignore it',
>> But this issue is from oVirt. So could you please help me.
>>
>> *Steps to reproduce :*
>> 1) Attach the disk to any VM
>> 2) Perform some read and write operation in the VM which will
>> increase the disk level - 'Read data rate / Write data rate /
>> disk.read.latency / disk.write.latency'
>> 3) Now when I bring down the VM, all the disk statistics should come
>> down to be zero *But it is still retaining with last known value
>> when the VM was in UP state.*
>>
>>
>> *Expected : All values should go to ZeroActual : All values retains
>> the last known values when the VM was in UP state. *
>>
>> Thanks,
>> Hari
>>
>>
>> On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg 
>> wrote:
>>
>>>
>>>
>>> On Jul 17, 2018 11:56, Hari Prasanth Loganathan >> msystechnologies.com> wrote:
>>>
>>> It is an issue from our side. Please ignore my question.
>>>
>>>
>>> You've now made several posts about wanting help, but this
>>> completely contradicts it!
>>>
>>>
>>> I don't get it, do you have an issue you want help with, or should
>>> everyone just ignore you?
>>>
>>> /K
>>>
>>>
>>> But How frequently we will collect the disk statistics and update in
>>> PostgreSQL?
>>>
>>> Thanks,
>>> Hari
>>>
>>> On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
>>> hariprasant...@msystechnologies.com> wrote:
>>>
>>> Hi Team,
>>>
>>> We are using the following API to collect the disk statistics,
>>>
>>> https://X.X.X.2/ovirt-engine/api/
>>> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
>>> 
>>>
>>> I found one issue in the disk statistics. In case If the Virtual
>>> Machine has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*)
>>> attached to it and I perform some read / write operation in the VM and 
>>> it
>>> increases the corresponding disk level Read data rate / Write data rate 
>>> /
>>> disk.read.latency / disk.write.latency.
>>>
>>> *Example*, I received the following values for this disk, But the
>>> problem is even when I bring down the VM still the last known value is
>>> received continuously.
>>> *Is it a known issue Or any workaround is available? *
>>>
>>> *Expected : All values should go to Zero*
>>>
>>> *Actual : All values retains the last known values when the VM was
>>> in UP state. *
>>>
>>>
>>> {
>>> "statistic": [
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "bytes_per_second",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 2184
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href": "/ovirt-engine/api/disks/
>>> 2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "data.current.read",
>>> "description": "Read data rate",
>>> "href": "/ovirt-engine/api/disks/
>>> 2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/
>>> 33b9212b-f9cb-3fd0-b364-248fb61e1272",
>>> "id": 

[ovirt-users] Re: Disk Statistics API in oVirt

[Andrej Krejcir]

Hi,

Looking at the code, the disk statistics are only updated when the VM is
running.
It looks like a bug. Could you open a Bugzilla ticket, so we can properly
fix it?

https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

Set the component to: Backend.Core
And oVirt Team to: Virt


Regards,
Andrej

On Mon, 30 Jul 2018 at 20:01, Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Thanks Greg, please let me know this.
>
>
> On Mon, 30 Jul 2018 at 11:29 PM, Greg Sheremeta 
> wrote:
>
>> Sorry for the delay. adding some others that may know.
>>
>> On Sun, Jul 29, 2018 at 11:02 PM Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>>> Hi Guys,
>>>
>>> Any update on this, please?
>>>
>>> Thanks,
>>> Hari
>>>
>>> On Fri, Jul 27, 2018 at 5:52 AM, Greg Sheremeta 
>>> wrote:
>>>
 + @Tomas Jelinek  do you know this one?

 On Wed, Jul 18, 2018 at 1:57 AM Hari Prasanth Loganathan <
 hariprasant...@msystechnologies.com> wrote:

> Hi Karli,
>
> Sorry for the confusion, Initially I thought it is an issue from our
> side so posted like 'ignore it',
> But this issue is from oVirt. So could you please help me.
>
> *Steps to reproduce :*
> 1) Attach the disk to any VM
> 2) Perform some read and write operation in the VM which will increase
> the disk level - 'Read data rate / Write data rate /
> disk.read.latency / disk.write.latency'
> 3) Now when I bring down the VM, all the disk statistics should come
> down to be zero *But it is still retaining with last known value when
> the VM was in UP state.*
>
>
> *Expected : All values should go to ZeroActual : All values retains
> the last known values when the VM was in UP state. *
>
> Thanks,
> Hari
>
>
> On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg 
> wrote:
>
>>
>>
>> On Jul 17, 2018 11:56, Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>> It is an issue from our side. Please ignore my question.
>>
>>
>> You've now made several posts about wanting help, but this completely
>> contradicts it!
>>
>>
>> I don't get it, do you have an issue you want help with, or should
>> everyone just ignore you?
>>
>> /K
>>
>>
>> But How frequently we will collect the disk statistics and update in
>> PostgreSQL?
>>
>> Thanks,
>> Hari
>>
>> On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>> Hi Team,
>>
>> We are using the following API to collect the disk statistics,
>>
>> https://X.X.X.2/ovirt-engine/api/
>> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
>> 
>>
>> I found one issue in the disk statistics. In case If the Virtual
>> Machine has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*)
>> attached to it and I perform some read / write operation in the VM and it
>> increases the corresponding disk level Read data rate / Write data rate /
>> disk.read.latency / disk.write.latency.
>>
>> *Example*, I received the following values for this disk, But the
>> problem is even when I bring down the VM still the last known value is
>> received continuously.
>> *Is it a known issue Or any workaround is available? *
>>
>> *Expected : All values should go to Zero*
>>
>> *Actual : All values retains the last known values when the VM was in
>> UP state. *
>>
>>
>> {
>> "statistic": [
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "bytes_per_second",
>> "values": {
>> "value": [
>> {
>> "datum": 2184
>> }
>> ]
>> },
>> "disk": {
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "data.current.read",
>> "description": "Read data rate",
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
>> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
>> },
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "bytes_per_second",
>> "values": {
>> "value": [
>> {
>> "datum": 41202005
>> }
>> ]
>> 

[ovirt-users] Re: Disk Statistics API in oVirt

[Hari Prasanth Loganathan]

Thanks Greg, please let me know this.


On Mon, 30 Jul 2018 at 11:29 PM, Greg Sheremeta  wrote:

> Sorry for the delay. adding some others that may know.
>
> On Sun, Jul 29, 2018 at 11:02 PM Hari Prasanth Loganathan <
> hariprasant...@msystechnologies.com> wrote:
>
>> Hi Guys,
>>
>> Any update on this, please?
>>
>> Thanks,
>> Hari
>>
>> On Fri, Jul 27, 2018 at 5:52 AM, Greg Sheremeta 
>> wrote:
>>
>>> + @Tomas Jelinek  do you know this one?
>>>
>>> On Wed, Jul 18, 2018 at 1:57 AM Hari Prasanth Loganathan <
>>> hariprasant...@msystechnologies.com> wrote:
>>>
 Hi Karli,

 Sorry for the confusion, Initially I thought it is an issue from our
 side so posted like 'ignore it',
 But this issue is from oVirt. So could you please help me.

 *Steps to reproduce :*
 1) Attach the disk to any VM
 2) Perform some read and write operation in the VM which will increase
 the disk level - 'Read data rate / Write data rate / disk.read.latency
 / disk.write.latency'
 3) Now when I bring down the VM, all the disk statistics should come
 down to be zero *But it is still retaining with last known value when
 the VM was in UP state.*


 *Expected : All values should go to ZeroActual : All values retains the
 last known values when the VM was in UP state. *

 Thanks,
 Hari


 On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg 
 wrote:

>
>
> On Jul 17, 2018 11:56, Hari Prasanth Loganathan <
> hariprasant...@msystechnologies.com> wrote:
>
> It is an issue from our side. Please ignore my question.
>
>
> You've now made several posts about wanting help, but this completely
> contradicts it!
>
>
> I don't get it, do you have an issue you want help with, or should
> everyone just ignore you?
>
> /K
>
>
> But How frequently we will collect the disk statistics and update in
> PostgreSQL?
>
> Thanks,
> Hari
>
> On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
> hariprasant...@msystechnologies.com> wrote:
>
> Hi Team,
>
> We are using the following API to collect the disk statistics,
>
> https://X.X.X.2/ovirt-engine/api/
> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
> 
>
> I found one issue in the disk statistics. In case If the Virtual
> Machine has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*)
> attached to it and I perform some read / write operation in the VM and it
> increases the corresponding disk level Read data rate / Write data rate /
> disk.read.latency / disk.write.latency.
>
> *Example*, I received the following values for this disk, But the
> problem is even when I bring down the VM still the last known value is
> received continuously.
> *Is it a known issue Or any workaround is available? *
>
> *Expected : All values should go to Zero*
>
> *Actual : All values retains the last known values when the VM was in
> UP state. *
>
>
> {
> "statistic": [
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 2184
> }
> ]
> },
> "disk": {
> "href":
> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.read",
> "description": "Read data rate",
> "href":
> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 41202005
> }
> ]
> },
> "disk": {
> "href":
> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.write",
> "description": "Write data rate",
> "href":
> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
> },
> 

[ovirt-users] Re: Disk Statistics API in oVirt

[Greg Sheremeta]

Sorry for the delay. adding some others that may know.

On Sun, Jul 29, 2018 at 11:02 PM Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Hi Guys,
>
> Any update on this, please?
>
> Thanks,
> Hari
>
> On Fri, Jul 27, 2018 at 5:52 AM, Greg Sheremeta 
> wrote:
>
>> + @Tomas Jelinek  do you know this one?
>>
>> On Wed, Jul 18, 2018 at 1:57 AM Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>>> Hi Karli,
>>>
>>> Sorry for the confusion, Initially I thought it is an issue from our
>>> side so posted like 'ignore it',
>>> But this issue is from oVirt. So could you please help me.
>>>
>>> *Steps to reproduce :*
>>> 1) Attach the disk to any VM
>>> 2) Perform some read and write operation in the VM which will increase
>>> the disk level - 'Read data rate / Write data rate / disk.read.latency
>>> / disk.write.latency'
>>> 3) Now when I bring down the VM, all the disk statistics should come
>>> down to be zero *But it is still retaining with last known value when
>>> the VM was in UP state.*
>>>
>>>
>>> *Expected : All values should go to ZeroActual : All values retains the
>>> last known values when the VM was in UP state. *
>>>
>>> Thanks,
>>> Hari
>>>
>>>
>>> On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg 
>>> wrote:
>>>


 On Jul 17, 2018 11:56, Hari Prasanth Loganathan <
 hariprasant...@msystechnologies.com> wrote:

 It is an issue from our side. Please ignore my question.


 You've now made several posts about wanting help, but this completely
 contradicts it!


 I don't get it, do you have an issue you want help with, or should
 everyone just ignore you?

 /K


 But How frequently we will collect the disk statistics and update in
 PostgreSQL?

 Thanks,
 Hari

 On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
 hariprasant...@msystechnologies.com> wrote:

 Hi Team,

 We are using the following API to collect the disk statistics,

 https://X.X.X.2/ovirt-engine/api/
 *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
 

 I found one issue in the disk statistics. In case If the Virtual
 Machine has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*)
 attached to it and I perform some read / write operation in the VM and it
 increases the corresponding disk level Read data rate / Write data rate /
 disk.read.latency / disk.write.latency.

 *Example*, I received the following values for this disk, But the
 problem is even when I bring down the VM still the last known value is
 received continuously.
 *Is it a known issue Or any workaround is available? *

 *Expected : All values should go to Zero*

 *Actual : All values retains the last known values when the VM was in
 UP state. *


 {
 "statistic": [
 {
 "kind": "gauge",
 "type": "decimal",
 "unit": "bytes_per_second",
 "values": {
 "value": [
 {
 "datum": 2184
 }
 ]
 },
 "disk": {
 "href":
 "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
 "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
 },
 "name": "data.current.read",
 "description": "Read data rate",
 "href":
 "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
 "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
 },
 {
 "kind": "gauge",
 "type": "decimal",
 "unit": "bytes_per_second",
 "values": {
 "value": [
 {
 "datum": 41202005
 }
 ]
 },
 "disk": {
 "href":
 "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
 "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
 },
 "name": "data.current.write",
 "description": "Write data rate",
 "href":
 "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
 "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
 },
 {
 "kind": "gauge",
 "type": "decimal",
 "unit": "seconds",
 "values": {
 "value": [
 {
 "datum": 0.12
   

[ovirt-users] Re: Disk Statistics API in oVirt

[Hari Prasanth Loganathan]

Hi Guys,

Any update on this, please?

Thanks,
Hari

On Fri, Jul 27, 2018 at 5:52 AM, Greg Sheremeta  wrote:

> + @Tomas Jelinek  do you know this one?
>
> On Wed, Jul 18, 2018 at 1:57 AM Hari Prasanth Loganathan  msystechnologies.com> wrote:
>
>> Hi Karli,
>>
>> Sorry for the confusion, Initially I thought it is an issue from our side
>> so posted like 'ignore it',
>> But this issue is from oVirt. So could you please help me.
>>
>> *Steps to reproduce :*
>> 1) Attach the disk to any VM
>> 2) Perform some read and write operation in the VM which will increase
>> the disk level - 'Read data rate / Write data rate / disk.read.latency /
>> disk.write.latency'
>> 3) Now when I bring down the VM, all the disk statistics should come down
>> to be zero *But it is still retaining with last known value when the VM
>> was in UP state.*
>>
>>
>> *Expected : All values should go to ZeroActual : All values retains the
>> last known values when the VM was in UP state. *
>>
>> Thanks,
>> Hari
>>
>>
>> On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg 
>> wrote:
>>
>>>
>>>
>>> On Jul 17, 2018 11:56, Hari Prasanth Loganathan >> msystechnologies.com> wrote:
>>>
>>> It is an issue from our side. Please ignore my question.
>>>
>>>
>>> You've now made several posts about wanting help, but this completely
>>> contradicts it!
>>>
>>>
>>> I don't get it, do you have an issue you want help with, or should
>>> everyone just ignore you?
>>>
>>> /K
>>>
>>>
>>> But How frequently we will collect the disk statistics and update in
>>> PostgreSQL?
>>>
>>> Thanks,
>>> Hari
>>>
>>> On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
>>> hariprasant...@msystechnologies.com> wrote:
>>>
>>> Hi Team,
>>>
>>> We are using the following API to collect the disk statistics,
>>>
>>> https://X.X.X.2/ovirt-engine/api/
>>> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
>>> 
>>>
>>> I found one issue in the disk statistics. In case If the Virtual Machine
>>> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it
>>> and I perform some read / write operation in the VM and it increases the
>>> corresponding disk level Read data rate / Write data rate /
>>> disk.read.latency / disk.write.latency.
>>>
>>> *Example*, I received the following values for this disk, But the
>>> problem is even when I bring down the VM still the last known value is
>>> received continuously.
>>> *Is it a known issue Or any workaround is available? *
>>>
>>> *Expected : All values should go to Zero*
>>>
>>> *Actual : All values retains the last known values when the VM was in UP
>>> state. *
>>>
>>>
>>> {
>>> "statistic": [
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "bytes_per_second",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 2184
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href": "/ovirt-engine/api/disks/
>>> 2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "data.current.read",
>>> "description": "Read data rate",
>>> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
>>> 2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
>>> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
>>> },
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "bytes_per_second",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 41202005
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href": "/ovirt-engine/api/disks/
>>> 2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "data.current.write",
>>> "description": "Write data rate",
>>> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
>>> 2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
>>> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
>>> },
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "seconds",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 0.12
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href": "/ovirt-engine/api/disks/
>>> 2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "disk.read.latency",
>>> "description": 

[ovirt-users] Re: Disk Statistics API in oVirt

[Greg Sheremeta]

+ @Tomas Jelinek  do you know this one?

On Wed, Jul 18, 2018 at 1:57 AM Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Hi Karli,
>
> Sorry for the confusion, Initially I thought it is an issue from our side
> so posted like 'ignore it',
> But this issue is from oVirt. So could you please help me.
>
> *Steps to reproduce :*
> 1) Attach the disk to any VM
> 2) Perform some read and write operation in the VM which will increase the 
> disk
> level - 'Read data rate / Write data rate / disk.read.latency /
> disk.write.latency'
> 3) Now when I bring down the VM, all the disk statistics should come down
> to be zero *But it is still retaining with last known value when the VM
> was in UP state.*
>
>
> *Expected : All values should go to ZeroActual : All values retains the
> last known values when the VM was in UP state. *
>
> Thanks,
> Hari
>
>
> On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg 
> wrote:
>
>>
>>
>> On Jul 17, 2018 11:56, Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>> It is an issue from our side. Please ignore my question.
>>
>>
>> You've now made several posts about wanting help, but this completely
>> contradicts it!
>>
>>
>> I don't get it, do you have an issue you want help with, or should
>> everyone just ignore you?
>>
>> /K
>>
>>
>> But How frequently we will collect the disk statistics and update in
>> PostgreSQL?
>>
>> Thanks,
>> Hari
>>
>> On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>> Hi Team,
>>
>> We are using the following API to collect the disk statistics,
>>
>> https://X.X.X.2/ovirt-engine/api/
>> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
>> 
>>
>> I found one issue in the disk statistics. In case If the Virtual Machine
>> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it
>> and I perform some read / write operation in the VM and it increases the
>> corresponding disk level Read data rate / Write data rate /
>> disk.read.latency / disk.write.latency.
>>
>> *Example*, I received the following values for this disk, But the
>> problem is even when I bring down the VM still the last known value is
>> received continuously.
>> *Is it a known issue Or any workaround is available? *
>>
>> *Expected : All values should go to Zero*
>>
>> *Actual : All values retains the last known values when the VM was in UP
>> state. *
>>
>>
>> {
>> "statistic": [
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "bytes_per_second",
>> "values": {
>> "value": [
>> {
>> "datum": 2184
>> }
>> ]
>> },
>> "disk": {
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "data.current.read",
>> "description": "Read data rate",
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
>> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
>> },
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "bytes_per_second",
>> "values": {
>> "value": [
>> {
>> "datum": 41202005
>> }
>> ]
>> },
>> "disk": {
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "data.current.write",
>> "description": "Write data rate",
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
>> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
>> },
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "seconds",
>> "values": {
>> "value": [
>> {
>> "datum": 0.12
>> }
>> ]
>> },
>> "disk": {
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "disk.read.latency",
>> "description": "Read latency",
>> "href":
>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/3a7b3f72-d035-3bb9-b196-e86a4eb34993",
>> "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
>> },

[ovirt-users] Re: Disk Statistics API in oVirt

[Hari Prasanth Loganathan]

Hi Karli,

Sorry for the confusion, Initially I thought it is an issue from our side
so posted like 'ignore it',
But this issue is from oVirt. So could you please help me.

*Steps to reproduce :*
1) Attach the disk to any VM
2) Perform some read and write operation in the VM which will increase the disk
level - 'Read data rate / Write data rate / disk.read.latency /
disk.write.latency'
3) Now when I bring down the VM, all the disk statistics should come down
to be zero *But it is still retaining with last known value when the VM was
in UP state.*


*Expected : All values should go to ZeroActual : All values retains the
last known values when the VM was in UP state. *

Thanks,
Hari


On Wed, Jul 18, 2018 at 11:20 AM, Karli Sjöberg  wrote:

>
>
> On Jul 17, 2018 11:56, Hari Prasanth Loganathan  msystechnologies.com> wrote:
>
> It is an issue from our side. Please ignore my question.
>
>
> You've now made several posts about wanting help, but this completely
> contradicts it!
>
>
> I don't get it, do you have an issue you want help with, or should
> everyone just ignore you?
>
> /K
>
>
> But How frequently we will collect the disk statistics and update in
> PostgreSQL?
>
> Thanks,
> Hari
>
> On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan  msystechnologies.com> wrote:
>
> Hi Team,
>
> We are using the following API to collect the disk statistics,
>
> https://X.X.X.2/ovirt-engine/api/
> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
> 
>
> I found one issue in the disk statistics. In case If the Virtual Machine
> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it and
> I perform some read / write operation in the VM and it increases the
> corresponding disk level Read data rate / Write data rate /
> disk.read.latency / disk.write.latency.
>
> *Example*, I received the following values for this disk, But the problem
> is even when I bring down the VM still the last known value is received
> continuously.
> *Is it a known issue Or any workaround is available? *
>
> *Expected : All values should go to Zero*
>
> *Actual : All values retains the last known values when the VM was in UP
> state. *
>
>
> {
> "statistic": [
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 2184
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.read",
> "description": "Read data rate",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 41202005
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.write",
> "description": "Write data rate",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "seconds",
> "values": {
> "value": [
> {
> "datum": 0.12
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.read.latency",
> "description": "Read latency",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/statistics/3a7b3f72-d035-3bb9-b196-e86a4eb34993",
> "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "seconds",
> "values": {
> "value": [
> {
> "datum": 1.4
> }
> ]
> },
> "disk": {
> "href": 

[ovirt-users] Re: Disk Statistics API in oVirt

[Karli Sjöberg]

On Jul 17, 2018 11:56, Hari Prasanth Loganathan  wrote:It is an issue from our side. Please ignore my question. You've now made several posts about wanting help, but this completely contradicts it!I don't get it, do you have an issue you want help with, or should everyone just ignore you?/KBut How frequently we will collect the disk statistics and update in PostgreSQL? Thanks,Hari  On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan  wrote:Hi Team,We are using the following API to collect the disk statistics,https://X.X.X.2/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statisticsI found one issue in the disk statistics. In case If the Virtual Machine has this disk (2331bad7-71ec-4fad-95bb-2b3449f3dbda) attached to it and I perform some read / write operation in the VM and it increases the corresponding disk level Read data rate / Write data rate / disk.read.latency / disk.write.latency.Example, I received the following values for this disk, But the problem is even when I bring down the VM still the last known value is received continuously. Is it a known issue Or any workaround is available? Expected : All values should go to ZeroActual : All values retains the last known values when the VM was in UP state. {    "statistic": [    {    "kind": "gauge",    "type": "decimal",    "unit": "bytes_per_second",    "values": {    "value": [    {    "datum": 2184    }    ]    },    "disk": {    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",    "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"    },    "name": "data.current.read",    "description": "Read data rate",    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",    "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"    },    {    "kind": "gauge",    "type": "decimal",    "unit": "bytes_per_second",    "values": {    "value": [    {    "datum": 41202005    }    ]    },    "disk": {    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",    "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"    },    "name": "data.current.write",    "description": "Write data rate",    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",    "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"    },    {    "kind": "gauge",    "type": "decimal",    "unit": "seconds",    "values": {    "value": [    {    "datum": 0.12    }    ]    },    "disk": {    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",    "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"    },    "name": "disk.read.latency",    "description": "Read latency",    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/3a7b3f72-d035-3bb9-b196-e86a4eb34993",    "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"    },    {    "kind": "gauge",    "type": "decimal",    "unit": "seconds",    "values": {    "value": [    {    "datum": 1.4    }    ]    },    "disk": {    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",    "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"    },    "name": "disk.write.latency",    "description": "Write latency",    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/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/2331bad7-71ec-4fad-95bb-2b3449f3dbda",    "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"    },    "name": "disk.flush.latency",    "description": "Flush latency",    "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/9c17ad7b-9ef1-3e8d-ad0a-ff8bee3925f0",    "id": "9c17ad7b-9ef1-3e8d-ad0a-ff8bee3925f0"    }    ]}Thanks,Hari 



DISCLAIMER - MSysTechnologies LLC This email message, 

[ovirt-users] Re: Disk Statistics API in Ovirt

[Hari Prasanth Loganathan]

These statistics give wrong result when the VM is down. Guys did you get
any update on this?

Any help is appreciated.

Thanks,
Hari

On Tue, 17 Jul 2018 at 5:47 PM, Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Hi Team,
>
> *Steps to reproduce :*
> 1) Attach the disk to any VM
> 2) Perform some read and write operation in the VM which will increase the 
> disk
> level - 'Read data rate / Write data rate / disk.read.latency /
> disk.write.latency'
> 3) Now when I bring down the VM, all the disk statistics needs to be zero *But
> it is still retaining with last known value when the VM was in UP state.*
>
>
>
> *Expected : All values should go to ZeroActual : All values retains the
> last known values when the VM was in UP state. *
>
> Thanks,
> Hari
>
>
>
> On Tue, Jul 17, 2018 at 3:39 PM, Hari Prasanth Loganathan <
> hariprasant...@msystechnologies.com> wrote:
>
>> Hi Guys,
>>
>> I think it is a serious issue, please let us know your thoughts?
>>
>>
>> On Tue, Jul 17, 2018 at 3:27 PM, Hari Prasanth Loganathan <
>> hariprasant...@msystechnologies.com> wrote:
>>
>>> Hi Team,
>>>
>>> We are using the following API to collect the disk statistics,
>>>
>>> https://X.X.X.2/ovirt-engine/api/
>>> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
>>> 
>>>
>>> I found one issue in the disk statistics. In case If the Virtual Machine
>>> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it
>>> and I perform some read / write operation in the VM and it increases the
>>> corresponding disk level Read data rate / Write data rate /
>>> disk.read.latency / disk.write.latency.
>>>
>>> *Example*, I received the following values for this disk, But the
>>> problem is even when I bring down the VM still the last known value is
>>> received continuously.
>>> *Is it a known issue Or any workaround is available? *
>>>
>>> *Expected : All values should go to Zero*
>>>
>>> *Actual : All values retains the last known values when the VM was in UP
>>> state. *
>>>
>>>
>>> {
>>> "statistic": [
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "bytes_per_second",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 2184
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href":
>>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "data.current.read",
>>> "description": "Read data rate",
>>> "href":
>>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
>>> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
>>> },
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "bytes_per_second",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 41202005
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href":
>>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "data.current.write",
>>> "description": "Write data rate",
>>> "href":
>>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
>>> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
>>> },
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "seconds",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 0.12
>>> }
>>> ]
>>> },
>>> "disk": {
>>> "href":
>>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda",
>>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>>> },
>>> "name": "disk.read.latency",
>>> "description": "Read latency",
>>> "href":
>>> "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics/3a7b3f72-d035-3bb9-b196-e86a4eb34993",
>>> "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
>>> },
>>> {
>>> "kind": "gauge",
>>> "type": "decimal",
>>> "unit": "seconds",
>>> "values": {
>>> "value": [
>>> {
>>> "datum": 1.4
>>> }
>>> ]
>>> },
>>> "disk": {
>>> 

[ovirt-users] Re: Disk Statistics API in Ovirt

[Hari Prasanth Loganathan]

Hi Team,

*Steps to reproduce :*
1) Attach the disk to any VM
2) Perform some read and write operation in the VM which will increase the disk
level - 'Read data rate / Write data rate / disk.read.latency /
disk.write.latency'
3) Now when I bring down the VM, all the disk statistics needs to be zero *But
it is still retaining with last known value when the VM was in UP state.*



*Expected : All values should go to ZeroActual : All values retains the
last known values when the VM was in UP state. *

Thanks,
Hari



On Tue, Jul 17, 2018 at 3:39 PM, Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Hi Guys,
>
> I think it is a serious issue, please let us know your thoughts?
>
>
> On Tue, Jul 17, 2018 at 3:27 PM, Hari Prasanth Loganathan  msystechnologies.com> wrote:
>
>> Hi Team,
>>
>> We are using the following API to collect the disk statistics,
>>
>> https://X.X.X.2/ovirt-engine/api/
>> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
>> 
>>
>> I found one issue in the disk statistics. In case If the Virtual Machine
>> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it
>> and I perform some read / write operation in the VM and it increases the
>> corresponding disk level Read data rate / Write data rate /
>> disk.read.latency / disk.write.latency.
>>
>> *Example*, I received the following values for this disk, But the
>> problem is even when I bring down the VM still the last known value is
>> received continuously.
>> *Is it a known issue Or any workaround is available? *
>>
>> *Expected : All values should go to Zero*
>>
>> *Actual : All values retains the last known values when the VM was in UP
>> state. *
>>
>>
>> {
>> "statistic": [
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "bytes_per_second",
>> "values": {
>> "value": [
>> {
>> "datum": 2184
>> }
>> ]
>> },
>> "disk": {
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "data.current.read",
>> "description": "Read data rate",
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-3fd
>> 0-b364-248fb61e1272",
>> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
>> },
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "bytes_per_second",
>> "values": {
>> "value": [
>> {
>> "datum": 41202005
>> }
>> ]
>> },
>> "disk": {
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "data.current.write",
>> "description": "Write data rate",
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-3d8
>> 2-a449-c28778bc33eb",
>> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
>> },
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "seconds",
>> "values": {
>> "value": [
>> {
>> "datum": 0.12
>> }
>> ]
>> },
>> "disk": {
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "disk.read.latency",
>> "description": "Read latency",
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/3a7b3f72-d035-3bb
>> 9-b196-e86a4eb34993",
>> "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
>> },
>> {
>> "kind": "gauge",
>> "type": "decimal",
>> "unit": "seconds",
>> "values": {
>> "value": [
>> {
>> "datum": 1.4
>> }
>> ]
>> },
>> "disk": {
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda",
>> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
>> },
>> "name": "disk.write.latency",
>> "description": "Write latency",
>> "href": "/ovirt-engine/api/disks/2331b
>> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/b1e75c7b-cea4-37d
>> 

[ovirt-users] Re: Disk Statistics API in Ovirt

[Hari Prasanth Loganathan]

Hi Guys,

I think it is a serious issue, please let us know your thoughts?


On Tue, Jul 17, 2018 at 3:27 PM, Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Hi Team,
>
> We are using the following API to collect the disk statistics,
>
> https://X.X.X.2/ovirt-engine/api/
> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
> 
>
> I found one issue in the disk statistics. In case If the Virtual Machine
> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it and
> I perform some read / write operation in the VM and it increases the
> corresponding disk level Read data rate / Write data rate /
> disk.read.latency / disk.write.latency.
>
> *Example*, I received the following values for this disk, But the problem
> is even when I bring down the VM still the last known value is received
> continuously.
> *Is it a known issue Or any workaround is available? *
>
> *Expected : All values should go to Zero*
>
> *Actual : All values retains the last known values when the VM was in UP
> state. *
>
>
> {
> "statistic": [
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 2184
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.read",
> "description": "Read data rate",
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/33b9212b-f9cb-
> 3fd0-b364-248fb61e1272",
> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 41202005
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.write",
> "description": "Write data rate",
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/2f23addd-4ebd-
> 3d82-a449-c28778bc33eb",
> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "seconds",
> "values": {
> "value": [
> {
> "datum": 0.12
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.read.latency",
> "description": "Read latency",
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda/statistics/3a7b3f72-d035-
> 3bb9-b196-e86a4eb34993",
> "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "seconds",
> "values": {
> "value": [
> {
> "datum": 1.4
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.write.latency",
> "description": "Write latency",
> "href": "/ovirt-engine/api/disks/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda/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/2331b
> ad7-71ec-4fad-95bb-2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.flush.latency",
> "description": "Flush latency",
> "href": "/ovirt-engine/api/disks/2331b
> 

[ovirt-users] Re: Disk Statistics API in oVirt

[Hari Prasanth Loganathan]

It is an issue from our side. Please ignore my question.

But How frequently we will collect the disk statistics and update in
PostgreSQL?

Thanks,
Hari

On Tue, Jul 17, 2018 at 3:18 PM, Hari Prasanth Loganathan <
hariprasant...@msystechnologies.com> wrote:

> Hi Team,
>
> We are using the following API to collect the disk statistics,
>
> https://X.X.X.2/ovirt-engine/api/
> *disks/2331bad7-71ec-4fad-95bb-2b3449f3dbda/statistics*
> 
>
> I found one issue in the disk statistics. In case If the Virtual Machine
> has this disk (*2331bad7-71ec-4fad-95bb-2b3449f3dbda*) attached to it and
> I perform some read / write operation in the VM and it increases the
> corresponding disk level Read data rate / Write data rate /
> disk.read.latency / disk.write.latency.
>
> *Example*, I received the following values for this disk, But the problem
> is even when I bring down the VM still the last known value is received
> continuously.
> *Is it a known issue Or any workaround is available? *
>
> *Expected : All values should go to Zero*
>
> *Actual : All values retains the last known values when the VM was in UP
> state. *
>
>
> {
> "statistic": [
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 2184
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.read",
> "description": "Read data rate",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/statistics/33b9212b-f9cb-3fd0-b364-248fb61e1272",
> "id": "33b9212b-f9cb-3fd0-b364-248fb61e1272"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "bytes_per_second",
> "values": {
> "value": [
> {
> "datum": 41202005
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "data.current.write",
> "description": "Write data rate",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/statistics/2f23addd-4ebd-3d82-a449-c28778bc33eb",
> "id": "2f23addd-4ebd-3d82-a449-c28778bc33eb"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "seconds",
> "values": {
> "value": [
> {
> "datum": 0.12
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.read.latency",
> "description": "Read latency",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/statistics/3a7b3f72-d035-3bb9-b196-e86a4eb34993",
> "id": "3a7b3f72-d035-3bb9-b196-e86a4eb34993"
> },
> {
> "kind": "gauge",
> "type": "decimal",
> "unit": "seconds",
> "values": {
> "value": [
> {
> "datum": 1.4
> }
> ]
> },
> "disk": {
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.write.latency",
> "description": "Write latency",
> "href": "/ovirt-engine/api/disks/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda/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/2331bad7-71ec-4fad-95bb-
> 2b3449f3dbda",
> "id": "2331bad7-71ec-4fad-95bb-2b3449f3dbda"
> },
> "name": "disk.flush.latency",
> "description": "Flush latency",
> "href":