How to instrument .NET agent via command line
Is there any way to inject .NET processes via command line, for automation purposes? The only information I have found thus far is on this page: .NET Agent Configuration#.NETAgentConfiguration-Command-LineOptions
It would be nice if an example of how to do this for iis app pools was included in the documentation page. We have 500-1000 .Net app pools in our environment I'm trying to POC and its hard to imagine instrumenting them click by click. The manual nature of this configuration has come up as a major drawback to the solution.
Rick,
What we've done before is automate the creation of the registry entries for the agent under HKLM\SOFTWARE\dynaTrace\Agent\Whitelist. So, in short we do the following with an automated deploy package. Depending on your tool you should be able to create something using these high level steps.
- Install dynaTrace agents via a silent install
- Detect what environment the machine is in
- Enumerate the AppPools on the machine
- Create registry entries with all proper information
- Recycle IIS
James,
can you please let us know about the detailed level steps to automate the dot net configration, sicne playing in the registry is quite risky.
Saravanan
be cautious of web servers on the same box as they may get mapped into the .NET application pools. But you can change those manually.
you can create a batch file. with this in side of it. Obviously you need to change AGENTNAME to match the name you would like to use.
setx DT_AGENTNAME ApplicationServer /M
setx DT_SERVER 10.10.10.1 /M
setx DT_ACTIVEAGENT true /M
Thanks Andreas,
I'll give this a shot today with easyTravel and figure it out. Appreciate the quick response!
Yes. All you need to do is to set these environment variables for that .NET Process. If you have e.g: a batch file to launch that EXE you can set the DT_XXX env variables to tell that process that dynaTrace should actively monitor it. You need to at least set the following variables:
- DT_AGENTNAME
- DT_SERVER
- DT_AGENTACTIVE
And of course you need to make sure that the .NET Agent is installed on that machine which will set the two global COR_XXX variables that are required by Microsoft. If you want to - you can also set these Env Variables in your script!
