# DiskIO on macOS **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [July 8, 2017, 7:32pm UTC](https://discuss.elastic.co/t/diskio-on-macos/92371 "2017-07-08T19:32:38Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![DPattee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpattee/32/37772_2.png) [@DPattee](https://discuss.elastic.co/u/DPattee)\ **Post date:** [July 8, 2017, 7:32pm UTC](https://discuss.elastic.co/t/diskio-on-macos/92371/1 "2017-07-08T19:32:39Z")
Any chance of getting diskio available for Mac / darwin servers? > System Diskio Metricset > The System diskio metricset provides disk IO metrics collected from the operating system. One event is created for each disk mounted on the system. > This metricset is available on: > Linux > Windows > FreeBSD (amd64) (I tried a forum search, didn't find anything relevant, if there is already a topic just fwd me to it) ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [July 10, 2017, 5:05am UTC](https://discuss.elastic.co/t/diskio-on-macos/92371/2 "2017-07-10T05:05:35Z")
It has been implemented for macOS in 6.x. The change is included in 6.0.0-alpha2 release. See the [change log](https://www.elastic.co/guide/en/beats/libbeat/master/release-notes-6.0.0-alpha2.html#_added). Please try the feature in the alpha release. ---
**Author:** ![DPattee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpattee/32/37772_2.png) [@DPattee](https://discuss.elastic.co/u/DPattee)\ **Post date:** [July 24, 2017, 3:17am UTC](https://discuss.elastic.co/t/diskio-on-macos/92371/3 "2017-07-24T03:17:26Z")
I've run the alpha for a little while now and it seems relatively stable for my light load and slow polling times. It could be interesting if the partitions were able to send data (disk0 as normal, but also disk0s1, s2, etc) but that info might not even be available in an easily consumable way haven't checked. I'm not convinced that the Files count is right, and in some cases it is definitely wrong. On a few of my drives I'm getting values which I haven't verified, but on most of them I'm getting 4,294,967,279 / FFFFFFEF which isn't quite a max uint32 unless I'm forgetting something about the math... ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [July 24, 2017, 2:10pm UTC](https://discuss.elastic.co/t/diskio-on-macos/92371/4 "2017-07-24T14:10:01Z")
I have seen issues with `files` on a few filesystems. IIRC some file systems report -1 in the `stat_t` struct when they don't implement this. What file systems were you seeing this problem with? ---
**Author:** ![DPattee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpattee/32/37772_2.png) [@DPattee](https://discuss.elastic.co/u/DPattee)\ **Post date:** [July 25, 2017, 4:59am UTC](https://discuss.elastic.co/t/diskio-on-macos/92371/5 "2017-07-25T04:59:07Z")
I'm testing on two Mac OS X Sierra machines (one is 10.12.5, the other is 10.12.6) ``` OS Version s.fs.files s.fs.mount_point File System s.fs.device_name OS X 10.12.15 4,294,967,279 / HFS+ Journaled /dev/disk0s2 OS X 10.12.15 4,294,967,279 /Volumes/ HFS+ Journaled /dev/disk1s2 OS X 10.12.15 4,294,967,279 /Volumes/ HFS+ Journaled /dev/disk2s2 OS X 10.12.15 652 /dev n/a devfs OS X 10.12.15 0 /net n/a map -hosts OS X 10.12.15 0 /home n/a map auto_home OS X 10.12.16 4,294,967,279 /Volumes/Recovery Apple_Boot /dev/disk0s3 OS X 10.12.16 4,294,967,279 / HFS+ Journaled /dev/disk1 OS X 10.12.16 4,294,967,279 /Volumes/ HFS+ Journaled /dev/disk2s2 OS X 10.12.16 4,294,967,279 /Volumes/Time Machine HFS+ /dev/disk3s2 OS X 10.12.16 1,205,990,864 /Volumes/ NTFS /dev/disk4s1 OS X 10.12.16 702 /dev n/a devfs OS X 10.12.16 0 /net n/a map -hosts OS X 10.12.16 0 /home n/a map auto_home OS X 10.12.16 1,465,014,458 /Volumes/ OSX 10.6.8’s Extended Journaled via AFP //@._afpovertcp._tcp.local/ ``` So, yea, looks like HFS+ is the one that is consistently broken. Now that I actually make a table of the data, I see a couple other 'things'... The primary drives on the Mac machines are mounted at /, true. But they do have names that are visible through _diskutil list_ or through an _ls /Volumes_, so there must be some way to pull the actual name. Mount points that aren't actually under the /dev/disk\* name space or under a /Volumes/ mount point are showing up. I can't think of a case where I'd want to have /dev show up in file system statistics. (And fwiw the /dev entry that claims 702 "files" actually has exactly half that many entries in an _ls /dev_ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 22, 2017, 4:59am UTC](https://discuss.elastic.co/t/diskio-on-macos/92371/6 "2017-08-22T04:59:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.