amalan_j wrote:
Hi,
I understand that the agents are created per worker process in .NET Application environment. In our environment we have one IntroscopeAgent.profile and the application is having 12 worker processes.
So we get 12 agents get created, but all the agents are sharing the same agent profile.
I have Two basic questions.
1. What's difference between Native Profiler and Auto Probe?
2. How do I Customize the agent creation and use differnt IntroscopeAgent.profile for each agent. This will help me to control the agent overhead.
Regards,
Amal
Hi Amal,
Below are the answers to your questions.
Answer 1:
NativeProfiler is the default instrumentation method for all .NET agents 9.0 and higher. AutoProbe is provided as an option for legacy compatibility issues.
By default, .NET agents use NativeProfiler to instrument applications, and all applications (and application pools) that run under IIS are instrumented. The instrumentation does not change the functionality of your applications. The probes are inserted into the bytecode to record application activity and send this information to the Enterprise Manager.
Note: When you install the .NET agent, you can choose NativeProfiler or AutoProbe to instrument your applications. AutoProbe is available primarily as a backup option for applications that cannot be instrumented with NativeProfiler or have legacy compatibility issues. CA Technologies recommends using NativeProfiler for all .NET agents unless you encounter compatibility issues.
Answer 2:
The .NET Framework permits configuration of application specific parameters using an optional XML format file with a .config extension.
For ASP.NET applications, web.config is the main file for application-specific settings and configuration. This file is stored in the application root directory.
For other .NET executables, the configuration file is named the same as the application appended with a .config extension. The file is stored in the same directory as the application executable. For example, for testapp.exe, the optional configuration file would be testapp.exe.config.
It is possible to add Introscope specific configuration to the .config file. For example, parameters can be set that enable individual applications to reference their own instance of the IntroscopeAgent.profile file (to permit different applications to have different agent configurations), as well as to enable cross-process transaction correlation for web services.
You basically create a separate IntroscopeAgent.profile for each of your applications. Then add a
sectionGroup and
section in the *.config file for your appliaction as follows:
<configuration>
<configSections>
<sectionGroup>
<sectionGroup name="com.wily.introscope.agent">
<section name="env.parameters"type="System.Configuration.NameValueSectionHandler" />
</sectionGroup>
<configSections>
<configuration>
Then add new properties to the
env.parameters section as follows:
<com.wily.introscope.agent>
<env.parameters>
<add key="com.wily.introscope.agentProfile" value="e:\\junkyard\\dotnettest\\Agent.profile" />
</env.parameters>
</com.wily.introscope.agent>
Repalce Agent.profile with the appropriate introscopeAgent.profile that you tailored for this application.
For an example, see
sample.exe.config file which is created in the %AGENT_HOME%\wily directory.
Note: All this information is available in
CA Wily Introscope .Net Agent Guide.pdf.
Hope you are satisfied with the answers. If yes, please mark your question as resolved.
Arij