Disk Avg.read time statistics not collected for a drive
kannappaganesh
Posts: 3
SQL monitor not collecting disk avg.read time and avg.disk queue length statistics for one drive (F: ) in a monitored server. Other logical disk counters are collected for the drive. For other drives in the machine, all statistics are collected.
Any idea what is causing this and suggestions for fix.
Any idea what is causing this and suggestions for fix.
Comments
Yes, we are monitoring a cluster with F: shared, but looking at the currently active node. The statistics for other counters like disk avg.write time etc.. are collected by SQL Monitor for F: drive. So, the drive is accessible.. Only the two avg read time and disk queue length are not collected.
That is most unfortunate as it's happening on a crucial drive.
Did you attempt to remove and re-add the cluster to SQLMonitor? I haven't tried that yet, but thought it might be worth a shot...
No guarantee it's going to stay the same the next time we perform a cluster failover though!
One thing I noted when removing the cluster and re-adding it was that before, it had cluster name, then under that, the nodes listed separately. And we could click node1, see stats, then node2, different stats for CPU, memory, etc, and so on with all nodes. After re-adding it, it was simply the cluster name with no nodes listed under it. So it appears they changed the way it handles clusters in some version or another. And my guess would be that the issue we're running in to is tied to that change somehow. Only a guess of course
Glad to hear yours is sorting itself out without having to lose any other data! I'll post back again to confirm that starting fresh 'fixes' it for us. How could it not though? New instance, new DB... if it doesn't, I'll really start getting concerned...