topic Re: How can I exclude entry points from deep monitoring or rather only instrument specific classess in certain methods in Real User Monitoring

How can I exclude entry points from deep monitoring or rather only instrument specific classess in certain methods

anthony_kalind1 — Wed, 26 Feb 2020 13:44:32 GMT

Enabling deep monitoring caused a service to become unresponsive with oneagent process cpu spiking quite high. Which makes sense some what, given that we are instrumenting a compiled exe.

In the appmon days we were able to instrument only specific entry points and exclude everything else.

With oneagent I can exlude incoming urls, but I would like to exclude or include specific entry points in deep monitoring.

Re: How can I exclude entry points from deep monitoring or rather only instrument specific classess in certain methods

justin_hogue — Wed, 26 Feb 2020 20:08:06 GMT

Hello,

Perhaps the use of custom services might help you here. Custom services can be created for Java, .NET, and PHP. They allow you to manually define methods, classes, or interfaces as entry points.

The use of process group rules might also be helpful. They allow you to create rules for defining what processes should be automatically deep monitored and detected.

I'll link documentation that further explains each below.

Custom service: https://www.dynatrace.com/support/help/shortlink/custom-services

Process group monitoring: https://www.dynatrace.com/support/help/shortlink/process-group-monitoring

Hope this helps!

Re: How can I exclude entry points from deep monitoring or rather only instrument specific classess in certain methods

ArunThilak_Rama — Thu, 21 Jan 2021 16:14:40 GMT

There are some valid use cases once in a while which required that we excluding certain classes from instrumentation because they dont work well with the OneAgent. Would like to have this feature.