Yes, DynaTrace OneAgent will crash the dbFront WebApplication if DynaTrace is configured with Process Injection enabled.
One of the ways that DynaTrace OneAgent works is by injecting monitoring logic into processes:
The DynaTrace OneAgent fails when it attempts to gain Debug Access to dbFront and inject its monitoring logic. This failure triggers an unrecoverable FastFail error. The FastFail error kills the dbFront IIS AppPool, blocking any access to dbFront. After multiple failures the IIS Rapid-Fail protection may stop the application completely. (IIS Rapid-Fail Protection)
Although DynaTrace's purposes are good, it should be noted that Debug Access is dangerous if abused because it allows runtime Memory Inspection, Code Injection and much more...
- Memory Inspection allows hackers to capture passwords and other high-value information,
- Code Injection gives hackers complete application control for their own malicious ends.
Because of this, gaining Debug Access is a very tempting exploit vector on web servers. The dbFront executables and libraries are purposely configured and signed to block debugging and code injection.
The solution is to disable Process Injection within DynaTrace. See: DynaTrace Configure Automatic Injection
Likely due to the way it raises the error (FastFail), DynaTrace OneAgent does not create any local log of the failure so there is no way to tie the application crash to DynaTrace. The only way to verify that DynaTrace OneAgent was the source of the issue, is to disable the Code Injection within DynaTrace or Uninstall DynaTrace OneAgent.