This post is more than 5 years old
6 Posts
0
159441
October 1st, 2012 12:00
vFoglight 6.7 - Disk request in Metric Graph
After upgrading to vFoglight 6.7 our Metric Graphs are not working as they did in 6.6.2. In 6.6.2 we used "Disk Read Requests" and "Disk Write Requests" but in 6.7 they don't display any data. I have tried to created a new Graph and used "Disk Write Requests RATE" but the result is not what i expected. If I compare the result with what VMware display it's totally different.
So, anyone else got this problem? Any solution?
No Events found!



DELL-Lee Ai
30 Posts
0
October 2nd, 2012 14:00
Hi Jens,
Looks like we need more information on this please open support case and one of our support Engineer will assist you from there.
Regards
-Lee
DELL-Lee Ai
30 Posts
0
October 1st, 2012 13:00
Hi Jens,
Which metric it refer to? Is that native VMware cartridge metric or it from v-Bundle or from other community cartridge?
-Lee
jenand1
6 Posts
0
October 1st, 2012 13:00
Hi Lee,
I'm not sure, but I find the metric via: Add view, VMware, Virtual Machines, , Storage, Disk Write Requests.
Regards
Jens
pgadgil
94 Posts
0
October 1st, 2012 14:00
Hello,
Did you upgrade your VMware Performance agent as well after upgrading vFoglight?
Sincerely
Prasad Gadgil
jenand1
6 Posts
0
October 1st, 2012 14:00
Yes, the VMware Performance agents has been updated, running version 5.6.4.2. I have noticed the same on a new installation at a customers site. We are runnning ESX 4.1 and the customer is running ESX 5.0.
Regards
Jens
dlarsen1
15 Posts
0
October 1st, 2012 21:00
Was the Agent Host (FglAM) also upgraded?
Administration | Agents | Agent Hosts
The vFoglight 6.7 version of the Agent Manager is 5.6.4.2
This is different than the agent itself:
Administration | Agents | Agent Status
5.6.4.2 is the latest VMware Performance Agent.
Thanks
-d
jenand1
6 Posts
0
October 2nd, 2012 05:00
Yes, FglAM was upgraded. Running version 5.6.2.4. But I can't find the FglAM version 5.6.4.2? VMware Performance Agent is running 5.6.4.2.
Regards
Jens
rachel sathya
22 Posts
0
October 2nd, 2012 11:00
Hi Jens,
The indication that the Fglam is on recent version can be found by going to Agent hosts dashboard & following the below steps.
Dashboards | Administration | Agents -> Agent Hosts.
Select your FgLAM host, on the bottom of this dashboard:
1. If the 'Upgrade' button is greyed out, it means your FgLAM is running current version 5.6.4.2.
2. If the upgrade button, is active, it means your on old FgLAM version & needs upgrade.
All you need to do, click 'Upgrade' & wait for green check mark on the pop-up window.
Then click OK -> hit refresh couple of times on this dashboard to see new version '5.6.4.2' for the upgraded FgLAm.
Hope this helps!
Best Regards,
Rachel
jenand1
6 Posts
0
October 2nd, 2012 12:00
Hi Rachel,
The upgrade button is greyed out, but the version is still 5.6.2.4.
The installfile for FglAM is named: fglam-5_6_2_4-windows-x86_x64.exe.
Under Administration it says: Server Version PRO 6.7.0 (build: 5.6.4.2-201208100802-249213)
Regards
Jens
rachel sathya
22 Posts
0
October 2nd, 2012 13:00
Hi Jens,
Apologies for version confusion here:
The FglAm version in vFoglight 6.7 is 5.6.2.4, it looks like your in the current version.
Only the Vmware agent version changed to 5.6.4.2.
Thanks,
Rachel
erikpmcg
13 Posts
0
January 22nd, 2014 04:00
Hi,
Have this issue been identified within Foglight for Virtualization. I've recently upgraded a couple of customers FMS to 7.0. There it seems the datastore reas/write counters are resuming collection.
But I do have another customer who know have requested a report in which I need these metrics for their ESXi hosts and thery are still on 6.7. I could use read/write rate: read rate = # blocksRead per second x blockSize
https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/disk_counters.html
But this doesn't show them what they need. Is it possible to convert these into Mb/s?
I've also found another metric, Disk Bytes Read/Written under Host Storage. Are these the same as the one I describe above, e.g. (See screenshot)
Regards,
Erik Alm