Showing results for 
Show  only  | Search instead for 
Did you mean: 
Dynatrace Guide
Dynatrace Guide

You don't have to disable OneAgent when an application is crashing, you can find the root cause by following the steps below. 

First please make sure you are using the supported version of technology by Dynatrace and also the latest version of OneAgent.

Technology support

It's a good approach to start the troubleshooting from the RUM (Real User Monitoring) and then do it deeper.
If a process is crashing first try to disable RUM for the process and check if this helps. You can disable RUM at the process group level and once it has done restart one agent.

Detailed step for disabling RUM.

If this solves the issue, please reach out to support for further help.

If this is not the problem, do the steps below.


Go to the process and identify the technology stack used in the process. You can find them by expanding the properties and tags section. 
Below is a sample. NET-based process, the steps are the same for all technology.


Identify the technologies used, then go to Settings -> Preferences -> OneAgent features->


Search for the technology censors and disable them one by one. Here we can try disabling IMBMQ, ADO.NET, WCF.

Make sure that you restart OneAgent after disabling each censor one at a time. In doing so for all censors you can identify the censor which is causing the issue. 

Once identified create a support ticket with the below details. 

Support ticket content


Version history
Last update:
‎04 May 2023 10:15 AM
Updated by:
DynaMight Legend
DynaMight Legend

Disabling the Dynatrace Oneagent should always be the very last option. Without it you risk insight into the true issue. @noel_david Thanks for sharing this!