Best way to disable .Net agent via command line
Hi,
I have a client that has multiple identical system in one location, where 1 of them is the 'master' system.
This master system can change from day to day.
Only the master system has to be instrumented with dynaTrace.
This system has a .Net agent in place.
My question: what would be the best way to disable the agent via command line. When the master system changes, we will have to disable the agent on one system and activate it on another.
In the doc I found the DT_AGENTACTIVE environment variable. Is setting that one to true and false enough to take of the agent? Will it remove all instrumentation? Is it the same as the Active/Inactive buttons on the agent configuration for .net utility?
Thanks for your help.
KR,
Kristof
Is there a similar way to disable java agents in a host rather than removing the entry from JVM startup.
-Sreerag
Could this be an RFE.
Global enable/disable will help in maintaining agent deployment using tools like Chef, Puppet. We could add agents on every server being built and enable agents when we are ready for profiling the application. I have seen where App team doesn't have enough time to setup agent (already in go live freeze) and went live without instrumentation. Once live its really hard to get agents on those applications.
-Sreerag
Perfect, thanks Roman.
Hi Kristof,
The active/inactive toggle in the agent configuration tool is setting or removing the environment variables COR_ENABLE_PROFILING and COR_PROFILER. If you have the capability of setting/removing environment variables that would be the easiest option.
Another idea would be to modify the entries in the agent whitelist (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\dynaTrace\Agent\Whitelist) in the Windows registry. You could just switch the active key from true to false and after a bounce of your IIS services the agent will no longer become active. It will still load - but then decide to not instrument the app. Consider setting DT_DISABLEINITIALLOGGING so that the agent does not log anything during the initial check of the whitelist.
Best, Roman
