Troubleshoot OneAgent deep-monitoring issues

Dynatrace OneAgent is supported on many platforms and offers deep monitoring for many technologies and frameworks. While the Dynatrace team does all it can to test all possible deep-monitoring scenarios, there may be situations where things don't work as planned. In order to streamline our support for such scenarios, we've added a Troubleshooting page (Settings > Server-side service monitoring > Deep monitoring).

Troubleshooting deep monitoring

Troubleshooting settings aren't used to configure OneAgent. Rather, they're used in combination with the Dynatrace Support team to resolve Support tickets related to OneAgent. These settings should't be used without guidance from Dynatrace Support. To choose an appropriate setting for troubleshooting in your environment, please work with Dynatrace support, as they will help determine the root cause of any detected issue.

The troubleshooting settings enable you to disable certain OneAgent functionality at a fine-grained level to facilitate issue resolution. This can be useful for identifying the root cause of a problem, all the way down to a specific feature. These settings also enable you to disable certain features that may be leading to problems while still retaining all other functionality while the Dynatrace Support team works on a permanent fix.

The new Troubleshooting settings page lists an assortment of deep monitoring features. Some of these are available for all code modules (for example, Capture PurePath) while others are technology-specific (for example, .NET ADO). Each feature can be turned off for the entire environment, a specific process group, or a single process. If a certain feature is problematic only in the context of a specific process group, you can disable the feature for just this process group and leave the rest of your environment untouched.

Some features like method hotspot information can only be turned on or off. These settings have an immediate effect as soon as you click the Save button in the upper right corner of the page. Most instrumentation features have two options:

  • Capturing off
    This setting has immediate effect and turns the specific feature off. This setting doesn't require a process restart. However, upon startup/restart of a process, the respective feature will still added to your application. Even while the feature is inactive, it can still have an impact on startup. The upside is that you can re-enable the feature without restarting any processes.
  • Instrumentation off
    This setting has the same immediate effect as Capturing off. However, upon restart/startup of a process, the feature won't be added to your application. This means that the feature will have no impact on your application. The downside is that, if you re-enable the feature later, you'll need to restart the affected processes.