We have struggled to troubleshoot some issues where an unknown component was calling Thread.interrupt(). Instrumenting the interrupt method has proven to be the quickest way to identify the code at fault. It would be very valuable to have a JFR event OOTB that records calls to interrupt() and captures the following:

- name / ID of thread calling interrupt()
- name / ID of target thread
- call stack of the calling thread