IIS sample instrumentation

Going through Instrumenting an IIS Manager is a matter of seconds.


You can set the environment variable %DT_HOME%, so you can reference it in paths. For example, for a default 64-bit AppMon installation, it is setx DT_HOME "C:\Program Files\dynaTrace\dynaTrace 6.5". You can also do it interactively in the System control panel.

To perform the configuration:

Open the Application Environment Configuration dialog box.


JavaScript Agent is injected automatically to HTML code of your website, so you don't have to perform additional configuration for the web application UEM, this is enabled by default. Make sure your license has some UEM volume for this to work.

Select the application type as Web / Java / .NET.

In the Webserver or PHP Engine step, click Add. The Configure Webserver or PHP Engine dialog box appears.

In the Web Server list, select Microsoft IIS. Keep the default name for it.

Select the machine, where the IIS installed and its architecture.

Replace the values for the Name and Server arguments in the %DT_HOME%/agent/conf/dtwsagent.ini file with the text from the dialog box, to change the name of the Agent and Collector to connect to.

Now, activate Dynatrace web server module for yours site.

Open the IIS Manager.

In the left panel, select the site you want to monitor.

In the IIS section of the middle panel, click Modules.

Check for the Dynatrace modules. If they are missing, in the right panel, click Configure Native Modules. If they are here, go to the step 12.

In the Configure Native Modules dialog box, select Dynatrace modules. You can select both 32- and 64-bit select Agents.

Restart the Dynatrace Web Server Agent service in Windows Services.

Restart or Recycle your IIS Application Pool in the IIS Manager.


For a Web server instrumentation you need two components: a running Web Server (master) Agent service and the actual Agent module loaded into the Web server.

If the message Successfully connected 2 Agents displays, instrumentation should work.

If the message Successfully connected 1 Agent displays, then only the Web Server Agent service runs. Something went wrong with the LoadModule.

If no message displays, then there is a problem with the Web Server Agent service and the state of the LoadModule injection (Agent 2) is unknown.

Close the summary dialog box.

Browse the site to make sure that components are actually loaded.