Can't disable DTrace :)

Though DTrace is "only" available on Windows, Mac OS X, Solaris, illumos, and FreeBSD.

Oracle has relicensed DTrace to be Linux-friendly and even made kernel patches, but it'll probably never end up in the mainline kernel.

On Linux you can use bpftrace which is basically the same thing with slightly different names.

> Though DTrace is "only" available on Windows

Is it stable and production ready for heavy duty workloads?

Microsoft ships it, so I assume so? I haven't personally ran any versions beyond Windows 7, I can't directly comment on any features after that.

You can use sysdig instead, which doesn't use ptrace[1] and is much faster (as well as generally more pleasant and powerful).

[1]It used to have its own kernel extension but is eEBF based these days.

Users should be aware that `sudo apt install sysdig` may require reconfiguration of UEFI Secure Boot, and that there is no apparent clean abort from this possible. The raw-mode terminal screen contains the text:

  ┌────────────────────────┤ Configuring Secure Boot ├────────────────────────┐
  │                                                                           │ 
  │ Your system has UEFI Secure Boot enabled.                                 │ 
  │                                                                           │ 
  │ UEFI Secure Boot requires additional configuration to work with           │ 
  │ third-party drivers.                                                      │ 
  │                                                                           │ 
  │ The system will assist you in configuring UEFI Secure Boot. To permit     │ 
  │ the use of third-party drivers, a new Machine-Owner Key (MOK) has been    │ 
  │ generated. This key now needs to be enrolled in your system's firmware.   │ 
  │                                                                           │ 
  │ To ensure that this change is being made by you as an authorized user,    │ 
  │ and not by an attacker, you must choose a password now and then confirm   │ 
  │ the change after reboot using the same password, in both the "Enroll      │ 
  │ MOK" and "Change Secure Boot state" menus that will be presented to you   │ 
  │ when this system reboots.                                                 │ 
  │                                                                           │ 
  │ If you proceed but do not confirm the password upon reboot, Ubuntu will   │ 
  │ still be able to boot on your system but any hardware that requires       │ 
  │ third-party drivers to work correctly may not be usable.                  │ 
  │                                                                           │ 
  │                                  <Ok>                                     │ 
  │                                                                           │ 
  └───────────────────────────────────────────────────────────────────────────┘

This leads to a second screen asking for a new password. There is a <Cancel> option, but selecting it merely loops back to the first screen.

Hitting C-c (Control-c) has no effect.

There are validity rules for the password, but they are presented only after you've entered an invalid password, twice, the second time to confirm.

After this installation proceeds, then terminates with a warning:

  DKMS: install completed.
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for libc-bin (2.31-0ubuntu9.9) ...
  W: Operation was interrupted before it could finish

Where the "W:" above is colored red.

Distro was Ubuntu 20.04.

I suspect that's just because you're trying to install an old version (as I wrote sysdig used to have a kernel extension but now should use eBPF functionality provided in stock kernels). I can't easily verify (no ubuntu at hand), but presumably if you install the vendor supplied, up-to-date version (first google hit I found: https://www.linuxcapable.com/how-to-install-sysdig-on-ubuntu...) it will work without UEFI changes.