DynaTrace agent causing powershell to throw stderror

Question

Question by Sreerag M. · Jan 14, 2014 at 09:29 PM ·

DynaTrace agent causing powershell to throw stderror

Hi,

When we run powershell.exe in one of the server where dynatrace .net agent is installed we are getting the following message.

[native] No Registry-Settings exist for this process
[native] Agent has no active settings - running normally

We dont have the agent configured to monitor the powershell process, wonder why is the agent trying to profile the powershell process.

Is this a know issue or is this how the .net agent works, i couldn't find nay details in the documentation on this.

-Sreerag

0

10 |2000000 characters needed characters left characters exceeded

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

Answer 1 · 2014-01-14T21:48:17Z

Answer by Ted F. · Jan 14, 2014 at 09:48 PM

Hey Sreerag,

You can set the environnment variable DT_DISABLEINITIALLOGGING=true globally. It suppresses logging of processes which are not supposed to be instrumented. I thought there's a KB article on it but I couldn't find it quickly - however my quick search at least brought up this other forum post.

thanks,
ted

1 · Share

10 |2000000 characters needed characters left characters exceeded

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

Answer 2 · 2014-01-14T21:51:38Z

Answer by Ted F. · Jan 14, 2014 at 09:51 PM

Update - I did find the KB article, but it is out of date. But, I checked the documentation and the DT_DISABLEINITIALLOGGING env var is detailed on this page.

===ted

0 Show 4 · Share

10 |2000000 characters needed characters left characters exceeded

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

Sreerag M. · Jan 14, 2014 at 09:57 PM 0

Share

Thanks Ted for the quick reply.

As i understand the setting will disable the Initial Logging which might work for us; Also would like to know if it is right to say that the agent checks every process(only .net?) to see if they have a valid configuration or not.

Andreas G. ♦ Sreerag M. · Jan 15, 2014 at 08:03 AM 1

Share

Hi Sreerag

When a .NET process starts and the registry key COR_PROFILER and COR_ENABLEPROFILING is set the .NET CLR will load the dynaTrace Agent in the process. Typically these two env variables are set system wide -> therefore the agent is loaded for every .net process. When it loads it checks whether there is an active configuration. It does so by looking in the registry (this is where the .NET Agent Config Tool stores the settings) - and also looks at additional env variables that you can also use to configure the process.

So - to answer your question: YES - the agent is typically loaded into every .NET Proceses and then verifies during startup if it should be active or not

Sreerag M. Andreas G. ♦ · Jan 16, 2014 at 02:30 AM 0

Share

Thanks Andi, that answers a lot. It is always good to know how things work.

Andreas G. ♦ Sreerag M. · Jan 16, 2014 at 08:27 AM 0

Share

happy to help - keep asking (smile)

BTW - I am still hoping for some good stories from you that we can use for the blog (smile)

DynaTrace agent causing powershell to throw stderror

2 Replies

How to get started

NAM 2019 SP5 is available

LIVE WEBINAR

Follow this Question

Forum Tags