I didn&#x27;t mean to be alarmist by posting this.  I actually think SIP is probably a good thing. I just wanted to raise awareness so folks don&#x27;t get bitten by it. I ran into this issue earlier trying to benchmark IO performance of my software on bare metal rather than in vagrant. Unfortunately, it seems iotop and iosnoop are broken unless I press this big red button that only experts can press to disable SIP, when all I want to do is a little system profiling. Maybe Activity Monitor has a scripting API I don&#x27;t know about. I&#x27;m just kind of annoyed by this, I would rather dual boot into Linux than having to restart into Recovery Mode to get basic IO profiling. I can understand that DTrace could be a privilege escalation risk, but maybe Apple has an official recommendation for how to properly use DTrace or an analogous API. `iostat` doesn&#x27;t cut it because I&#x27;m looking at a specific process which is run under my user.  I&#x27;m not using dtrace to reverse engineer system libraries. (I think) Apple already compiles dtrace with hooks so that it won&#x27;t trace specific processes to mitigate reverse engineering, which I can deal with. But hell, even `htop` is totally wrong now as I compare it to what Activity Monitor is showing.