We had a situation where a customer was suggesting APM overhead was causing poor performance during a load test. I suggested the nuclear option--delete the APM profiles, bounce IIS, and test without it. They accepted, and I deleted the profiles, cycled IIS, and went as far as confirming PMonitor.config and starter.config were 'clean'.
The next day during testing I was asked why APM was still running--someone had RDP'd, noticed the APM service was still running, and set it to disabled. While I could show them the config files, they have a point, the service does remain running. I offered to pose the question on their behalf, and was hoping someone here could explain why the APM service doesn't go back to Disabled.
Thanks!