Separate agent for .NET web application

Document ID : KB000020346
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

To instrument different .net web applications independently, so that options can be customized per application

Solution:

To instrument a .Net web application separately from the default:

Create a new application pool in IIS

Set the application to be instrumented to use the newly-created apppool.

Create a new profile for the application

Take the .Net agent's configuration, and copy it to another file in the same directory, renaming it to:

IntroscopeAgent.[MYAPPLICATION].profile

Then modify the parameters of the profile to fit the instrumentation of your application - whatever changes you want that differ from the default, you would make them in this new file.

Make sure to list ONLY the appropriate application pool (created above) specifically for this application.

Add sections to the application's web.config file:

Insert the section below on the line just before the line with the </configsections> tag.
<sectionGroup name="com.wily.introscope.agent">
<section name="env.parameters" type="System.Configuration.NameValueSectionHandler />
</sectionGroup>

Modify as appropriate (Items marked in CAPS between brackets) and add this section to the web.config file, just before the </configuration> tag:
<com.wily.introscope.agent>
<env.parameters>
<add key="com.wily.introscope.agentProfile" value="[YOUR PATH TO APM .NET AGENT]\Program Files\CA APM\Introscope 9.xxx\wily\IntroscopeAgent.[MYAPPLICATION].profile" />
</env.parameters>
</com.wily.introscope.agent>

Restart IIS, and a new entry should appear in the investigator tree, representing this application.