Hi there,
I understand cumulating IOs under datastore - Disk I/O makes sense to have a single view of how many IOs are thrown from a specific host/VM or against a specific datastore.
But when it comes to latencies, this makes no sense at all.
For example, monitoring READ Latency on all datastores from a VM sight shows peaks up to 250ms - which could mean every VM has a latency of 0,25ms (as we utilize about 1000VMs) or no VMs show latencies except one, which has 250ms.
Is there an ability to change this setting for latencies?
If not, could this be realized in coming versions?
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jun 26, 2017 12:34 pm
- Contact:
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Latencies cumulated in graphs
Hi and welcome to the community!
We did have such a bug in previous versions. Could you name exact graph where you see the latency summary?
What product version are you at?
Thanks!
We did have such a bug in previous versions. Could you name exact graph where you see the latency summary?
What product version are you at?
Thanks!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jun 26, 2017 12:34 pm
- Contact:
Re: Latencies cumulated in graphs
Hi, thanks for your reply.
We are on 9.5 U1.
We see this in the graph Infrastructure View - Clustername - Datastores - Disk IO
I do not think its a bug, as it is mentioned within documentation...
We are on 9.5 U1.
We see this in the graph Infrastructure View - Clustername - Datastores - Disk IO
I do not think its a bug, as it is mentioned within documentation...
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Latencies cumulated in graphs
Thanks, we will investigate the issue with QA team.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Latencies cumulated in graphs
We could not reproduce the issue, so please contact Veeam technical support for closer investigation.
Thanks!
Thanks!
Who is online
Users browsing this forum: No registered users and 9 guests