Missing metrics when specifying a new agent Profile for an Application

Document ID : KB000113496
Last Modified Date : 10/09/2018
Show Technical Document Details
Introduction:
The APM .Net Agent documentation provides the steps to configure a different profile for a particular application.
Basically the procedure consist in editing the web.config file of that particular application and adding the <configSections> and <com.wily.introscope.agent> sections from the <Agent_Home>\Sample.exe.config file. 

There are situations though where only the agent's metrics are seen in Investigator and none of the application's.


 
Background:
The procedure is described at this section in the documentation:

https://docops.ca.com/ca-apm/10-7/en/implementing-agents/microsoft-net-agent/configure-the-net-agent/configure-net-agent-properties#Configure.NETAgentProperties-Createseparateprofilesforeachapplication
Environment:
This procedure is applicable to all APM .Net agent versions
Instructions:
Documentation states that the only change is to edit the corresponding web.config but it fails to mention that all paths in the profile file are relative to its own location.

For example, if the profile contains the following entry:
           introscope.autoprobe.directivesFile=default-typical.pbl,hotdeploy 
then the agent will look for those files at the same path where the new profile file resides. 

If the new profile is created at the same level than the default IntroscopeAgent.profile, WILY_HOME,  then it will work just fine. However, if the new profile file is created in a folder other than the initial agent install path, then the directives will not be found and no metrics will be gathered for the application.

The missing steps are:

1- create a logs folder under the new path
2- copy all the pbd and pbl from WILY_HOME to the new path
3- copy the folders ext, hotdeploy and dynamic to the new path
4- if different log settings is needed, copy also logging.config.xml to the new path
5- Restart the application