DX Application Performance Management

How do you disable the .NET agent without un-installing it? In JAVA you just remove the arguments in the java options. Hopefully it is that simple with the .NET agent.

Hi,

For removing the agent in .Net you must change introscopeAgent.profile file to disable autoprobe and then remove the applications pools from monitoring, example:

introscope.autoprobe.enable=false
introscope.agent.dotnet.monitorAppPools= "dummy"

Telmo

I see this was posted long years back. The .net instrumentation have been improvsed over the years. there is no need to mess with the app pool monitoring unless needed.

in the "resticted instrumenation" portion of the "introscopeAgent.profile", only managed applicaiton / applications pool  for IIS 6.0  and above are instrumented automatically. Eveeything else reamins disabled until one enables it. In 9.5 it looks as below -

# To restrict instrumentation to ASP.NET applications only, set the property
# introscope.agent.dotnet.monitorApplications to w3wp.exe for IIS 6.0 or later
# and aspnet_wp.exe for IIS 5.  Add additional executable names to the list
# to instrument them.  Full pathnames with single backslashes are also
# acceptable.  For example,
# c:\windows\microsoft.net\framework\v1.1.4322\aspnet_wp.exe.

introscope.agent.dotnet.monitorApplications=w3wp.exe,aspnet_wp.exe ----> only this is enabled for my apps
 
# Uncomment the following property and specify IIS application pools to be instrumented.
# Application pool names must be in quotes. Use "NULL" to specify applications not running in any application pool.
#introscope.agent.dotnet.monitorAppPools= "NULL","DefaultAppPool","AppPool1","AppPool2"

 

 

Actually I would say the easiest option is to disable this at system level:
Cor_Enabling_Profilng=0x0

With the other options, the agent will still be loaded into the process even if it won’t be doing much, whereas this option completely stops profiling on the machine

David Lewis
Sr Support Engineer

CA Technologies | Riding Court Road | Datchet, Berkshire, SL39LL
Office: +44 1753 242570 | David.Lewis@ca.com

<mailto:David.Lewis@ca.com>[CA]<http://www.ca.com/us/default.aspx>[Facebook]<https://www.facebook.com/CATechnologies>[Twitter]<http://twitter.com/CAInc>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>
P Please consider the environment before printing this e-mail.
From: CA APM/Wily Global User CommunityMessage Boards [mailto:CommunityAdmin@communities-mail.ca.com]
Sent: 14 November 2013 19:56
To: mb_message.2307983.104724860@myca-email.ca.com
Subject: [CA APM General Discussion] RE: Remove .NET agent without un-installing.


I see this was posted long years back. The .net instrumentation have been improvsed over the years. there is no need to mess with the app pool monitoring unless needed.

in the "resticted instrumenation" portion of the "introscopeAgent.profile", only managed applicaiton / applications pool for IIS 6.0 and above are instrumented automatically. Eveeything else reamins disabled until one enables it. In 9.5 it looks as below -

# To restrict instrumentation to ASP.NET applications only, set the property
# introscope.agent.dotnet.monitorApplications to w3wp.exe for IIS 6.0 or later
# and aspnet_wp.exe for IIS 5. Add additional executable names to the list
# to instrument them. Full pathnames with single backslashes are also
# acceptable. For example,
# c:\windows\microsoft.net\framework\v1.1.4322\aspnet_wp.exe.

introscope.agent.dotnet.monitorApplications=w3wp.exe,aspnet_wp.exe ----> only this is enabled for my apps

# Uncomment the following property and specify IIS application pools to be instrumented.
# Application pool names must be in quotes. Use "NULL" to specify applications not running in any application pool.
#introscope.agent.dotnet.monitorAppPools= "NULL","DefaultAppPool","AppPool1","AppPool2"




Posted by:performance_guru
--
CA Communities Message Boards
104727400
mb_message.2307983.104724860@myca-email.ca.com<mailto:mb_message.2307983.104724860@myca-email.ca.com>
https://communities.ca.com

Sorry, I meant



Cor_Enable_Profiling=0x0

David Lewis
Sr Support Engineer

CA Technologies | Riding Court Road | Datchet, Berkshire, SL39LL
Office: +44 1753 242570 | David.Lewis@ca.com

<mailto:David.Lewis@ca.com>[CA]<http://www.ca.com/us/default.aspx>[Facebook]<https://www.facebook.com/CATechnologies>[Twitter]<http://twitter.com/CAInc>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>
P Please consider the environment before printing this e-mail.
From: CA APM/Wily Global User CommunityMessage Boards [mailto:CommunityAdmin@communities-mail.ca.com]
Sent: 15 November 2013 10:00
To: mb_message.2307983.104756604@myca-email.ca.com
Subject: [CA APM General Discussion] RE: [CA APM General Discussion] RE: Remove .NET agent without un-installing

Actually I would say the easiest option is to disable this at system level:
Cor_Enabling_Profilng=0x0

With the other options, the agent will still be loaded into the process even if it won’t be doing much, whereas this option completely stops profiling on the machine

David Lewis
Sr Support Engineer

CA Technologies | Riding Court Road | Datchet, Berkshire, SL39LL
Office: +44 1753 242570 | David.Lewis@ca.com<mailto:David.Lewis@ca.com>

<mailto[emoticon]avid.Lewis@ca.com><http://www.ca.com/us/default.aspx><https://www.facebook.com/CATechnologies><http://twitter.com/CAInc><http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1<mailto:avid.Lewis@ca.com%3e%3chttp://www.ca.com/us/default.aspx%3e%3chttps://www.facebook.com/CATechnologies%3e%3chttp://twitter.com/CAInc%3e%3chttp://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>>
P Please consider the environment before printing this e-mail.
From: CA APM/Wily Global User CommunityMessage Boards [mailto:CommunityAdmin@communities-mail.ca.com]
Sent: 14 November 2013 19:56
To: mb_message.2307983.104724860@myca-email.ca.com<mailto:mb_message.2307983.104724860@myca-email.ca.com>
Subject: [CA APM General Discussion] RE: Remove .NET agent without un-installing.


I see this was posted long years back. The .net instrumentation have been improvsed over the years. there is no need to mess with the app pool monitoring unless needed.

in the "resticted instrumenation" portion of the "introscopeAgent.profile", only managed applicaiton / applications pool for IIS 6.0 and above are instrumented automatically. Eveeything else reamins disabled until one enables it. In 9.5 it looks as below -

# To restrict instrumentation to ASP.NET applications only, set the property
# introscope.agent.dotnet.monitorApplications to w3wp.exe for IIS 6.0 or later
# and aspnet_wp.exe for IIS 5. Add additional executable names to the list
# to instrument them. Full pathnames with single backslashes are also
# acceptable. For example,
# c:\windows\microsoft.net\framework\v1.1.4322\aspnet_wp.exe.

introscope.agent.dotnet.monitorApplications=w3wp.exe,aspnet_wp.exe ----> only this is enabled for my apps

# Uncomment the following property and specify IIS application pools to be instrumented.
# Application pool names must be in quotes. Use "NULL" to specify applications not running in any application pool.
#introscope.agent.dotnet.monitorAppPools= "NULL","DefaultAppPool","AppPool1","AppPool2"




Posted by:performance_guru
--
CA Communities Message Boards
104727400
mb_message.2307983.104724860@myca-email.ca.com<mailto:mb_message.2307983.104724860@myca-email.ca.com<mailto:mb_message.2307983.104724860@myca-email.ca.com%3cmailto:mb_message.2307983.104724860@myca-email.ca.com>>
https://communities.ca.com Posted by:DavidLewis
--
CA Communities Message Boards
104759144
mb_message.2307983.104756604@myca-email.ca.com<mailto:mb_message.2307983.104756604@myca-email.ca.com>
http://communities.ca.com