OMI tables _SCXDiskDrive and _SCXDiskDriveStatisticalInformation are showling all disk drives except the ones behind a RAID 0.
Disk Stats seems to be correctly populated, but the omi is not aligned with it.
This issue prevents other Azure Extensions like Linux Azure Diagnostic 3.0 to collect disk metrics and potentially detect Throttling at Disk Level.
In sample below, disk drives 'sdd' and 'sdf' are configured in a RAID 0 array with mdadm, and mounted on ‘/p10_RAID’.
OS : Ubuntu Linux 16.04 LTS
Attached 4 data disks to VM:
2x Premium P10 (128 GB - Disk limits: 500 IOPS or 100 MB/s - Disk Cache Setting: None) - sdd + sdf
1x Premium P20 (512 GB - Disk limits: 2300 IOPS or 150 MB/s - Disk Cache Setting: None) - sde
1x Premium P30 (1024 GB - Disk limits: 5000 IOPS or 200 MB/s - Disk Cache Setting: None) - sdc
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 30G 0 disk
└─sda1 8:1 0 30G 0 part /
sdb 8:16 0 14G 0 disk
└─sdb1 8:17 0 14G 0 part /mnt
sdc 8:32 0 1023G 0 disk
└─sdc1 8:33 0 1023G 0 part /p30
sdd 8:48 0 127G 0 disk
└─sdd1 8:49 0 127G 0 part
└─md127 9:127 0 253.9G 0 raid0 /p10_RAID
sde 8:64 0 511G 0 disk
└─sde1 8:65 0 511G 0 part /p20
sdf 8:80 0 127G 0 disk
└─sdf1 8:81 0 127G 0 part
└─md127 9:127 0 253.9G 0 raid0 /p10_RAID
OMI tables _SCXDiskDrive and _SCXDiskDriveStatisticalInformation are showling all disk drives except the ones behind a RAID 0. Disk Stats seems to be correctly populated, but the omi is not aligned with it.
This issue prevents other Azure Extensions like Linux Azure Diagnostic 3.0 to collect disk metrics and potentially detect Throttling at Disk Level.
In sample below, disk drives 'sdd' and 'sdf' are configured in a RAID 0 array with mdadm, and mounted on ‘/p10_RAID’.
OS : Ubuntu Linux 16.04 LTS Attached 4 data disks to VM:
Below system disk stats information:
Below the OMI query: