Julius L. avatar image
Julius L. asked ·

What is the policy for automatic instrumentation?

We have a Windows 2012 server with an application consisting of many .NET processes (>30). After agent installation, all of the .NET processes are not instrumented (e.g. monitoring is disabled by default on the process group level). I have to enable monitoring of each process group individually.

What are the reasons for it? No known NET framework used in the processes? Not listening on TCP port?

Dynatrace Manageddynatrace saasmonitoringprocess groupsauto-detection
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Answer

Himanshu M. avatar image
Himanshu M. answered ·

Hi Julius , how are you manually enabling the monitoring ?

By .NET processes restart ?

3 comments Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

No I'm very well aware the process must be restarted to be deeply instrumented.

I have to to process group setting and manually change the setting, see here:

After turning the monitoring on for the individual process group and host I have to restart the process to get the deep instrumentation working (that's ok).

Is this something Windows specific / Application specific / NET specific? I thought that all processes of known technologies for deep instrumentation will be automatically monitored on Linux or Windows hosts.

0 Likes 0 · ·
pgis.png (218.0 KiB)

Hello @Julius L. , i have noticed the exact similar behaviour as mentioned by you in snapshot.

have you received an answer on this or not? P

0 Likes 0 · ·

Well, not yet. I've noticed this behaviour with just one application (don't have access to other instances of this app). I believe this app is probably not directly instrumentable (obfuscated or packaged), so Dynatrace turns off the monitoring for this process.

0 Likes 0 · ·

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions diagnostic tools session replay permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android