Yes please review https://docs.appdynamics.com/display/PRO44/Configure+the+.NET+Agent+for+Windows+Services+and+Standalone+Applications ... View more

You just have to restart the IIS. After restart CLR will load the profiler which will try and connect with Coordinator to identify whether this process needs to instrumented or not. Since Coordinator is stopped, Profiler will not get the response back from Coordinator and instrumentation will not happen. Thanks, Raunak ... View more

Hi, Do these nodes represent different Windows Services ? Thanks, Raunak ... View more

Hi,   All you need to do is identify the .Net Process under which this code is getting executed and then create a standalone app configuration and POCO rules to get the metrics. Thanks, Raunak ... View more

Hi Soundarajan, Yes that is expected. Agent is actually loaded into the instrumented process so after stopping Agent Coordinator Service you have to actually recycle the instrumented process/IIS. Thanks, Raunak ... View more

Hi,   If the name of the executable remains same after each deployment then you can always give just to executable name. If multiple instances of the same executable ( from different paths) can run then you can distinguish them using command line arguments. Otherwise, all instances will get identified and report to dynamically identified node names. Thanks, Raunak ... View more

Hi, Sorry this is what I explained in first two line full-no-dependency-mode : This config is specific to .Net Profiler which helps it to identify what modules are loaded in the process. This also helps detect dynamically loaded assemblies and how the agent is instrumenting them. This is extremely internal to .Net CLR Profiler implementation Thanks, Raunak ... View more

Hi,   We will need to figure out why Agent stopped reporting suddenly. Were there any planned activities executed around the time like server restart or AppPool recycle? After restarting Coordinator service have you tried restarting IIS/Instrumented application as well? If not please try and verify if Agents come back up Thanks, Raunak ... View more

Hi Haysam,   Can you confirm the type of BT that is getting idenOOTB? OOTB ? Is it Asp.net/WCF/Web Services or anything else? If you exclude the Parent BT, then you should be able to create a POCO rule and split it the way you want. Also if the Parent BT was identified as Asp.Net then you can create a Asp.net Custom Match Rule with higher preference and that will take preference. But if you create a POCO rule then it will not get the preference. Again if you could send out some screenshots of what you have tried that that has not worked we will be happy to help. Thanks, Raunak ... View more

Hi,   Had a quick discussion with the team and seems like you might be hitting limitation as described in the following document https://docs.appdynamics.com/pages/viewpage.action?pageId=45490396#AppAgentNodeProperties(M-R)-max-service-end-points-per-thread You may want to increase the node value but I suggest you review my previous update which should give you deeper insight. Thanks, Raunak ... View more

Hi  haysam,   I will run few tests to verify if SEP will not work in this scenario. But I will like to understand the reason behind trying to creating an entry point on already tracked code path. In case you will like to collect data from these methods ( like from method parameter or return value) then  Method Invocation Data Collector is way forward. https://docs.appdynamics.com/display/PRO44/Data+Collectors The collected data will show up in transaction snapshots. Thanks, Raunak ... View more

You have two options 1) Disable OOTB BT identification at Method1 and create POCOs on Method2 and Method3 to track them 2) Create Service End Points on these Methods https://docs.appdynamics.com/display/PRO44/Service+Endpoint+Detection#ServiceEndpointDetection-ConfigureServiceEndpointsfor.NET Ideally, you do not need to track these methods separately because they are already part of an ongoing BT and in case they are slowing down the BT will track it in form of snapshots. You can also create InforMation Points on these methods in case you just want to track basic metrics like ART, Call/Min, errors etc https://docs.appdynamics.com/display/PRO44/Information+Points Thanks, Raunak ... View more

Hi,   If the private methods you are trying to create Custom Match Rule on is oart of on-going BT then new BTs will not be created. For example if you have a class definition like this Class Test{   Private void Method1(){ Method2(); } Private Method2(){ Method3(); } Private Method3(){ DoSomething(); } } And you create a POCO rule on  Class : Test Method : Method1 Then creating other rules on same Class and different methods called by Method1 like Method2, Method3 will not yield new BTs are then are part of BT started for Method1 Let us know if you are talking about a different scenario. Please provide screenshots where necessary. Thanks, Raunak ... View more

Hi,  Instead of changing OOTB Rule, can you try creating Custom Match Rule with the configuration described in the screenshot? Basically URL contains "Cars_Sample_App/enquire.do" and split via Http Param "query"  ... View more

Sure Yogesh. Let us know if you see significant overhead. We will move this case to Support portal so that we investigate this in more detail. Thanks, Raunak ... View more

Hi Tudor,   Can you double check that both ssl and enable_tls12 is set to true like shown below? <controller host="mycontroller.mycompany.com" port="443" ssl="true" enable_tls12="true"  If above does not work, can you also double check if port 443 is not blocked in anyway. Thanks, Raunak ... View more

Hi Sandeep,   Glad to hear that you are able to instrument .net application now. For the benefit of other community users can you provide some details what was the issue and how did you go about fixing it? Thanks, Raunak ... View more

Hi,   Any reason you want to instrument Agent Coordinator service ? The reason I ask is .net Agent has two parts to it. First is the Agent Coordinator Service which runs as a Windows Service and second is actuall agent which gets loaded with instrumented application's memory space. You wont be able to monitor the actial Agent's resource consumption via configurations because its part of instrumented application. But if you belive agent is causing signifact overhead you should run your load/performance tests with and with out agent to find out how much overhead ( CPU/Memory/ART/Throuput etc) is added For Agent Coordinator Service you can but you do not need to instrument the Cordinator service. If all you care is about Memory,CPU etc metrics then you can just import relevant performance counter for Agent Coordinator service https://docs.appdynamics.com/display/PRO44/Manage+Windows+Performance+Metrics Thanks, Raunak ... View more

Hi Emrul,  .net Agent does not intrument IIS but .Net applications hosted in IIS. Please verify if you have .Net applications hosted on your IIS or not. Thanks, Raunak ... View more

Hi Yogesh,   Do you mean you are seeing higher response times with Agent when compared to without Agent? Controller installation has nothing to do with Agent performance until unless Controller on the same server was causing resource crunch at server level ultimately affecting the performance of your instrumentation application. Also, you may see higher response times in an initial couple of mins with Agent as Agent is applying instrumentation during the startup of the process. Can you run a load test and share with us results you see in terms of ART with and without agent/ Thanks, Raunak ... View more

It means that Windows has cached these variables. Restarting the server should help. ... View more

Hi,   We do not create these variables at the Registry level. Please check System Environment variables and verify their presence. If they exist please delete them. Just restarting the server should fix these messages as well. Thanks, Raunak ... View more

Everytime a .Net Process comes to life it checks two Environment Variable. 1) COR_ENABLE_PROFILING : If the value of this environment variable is 1, it indicates that  profiling is enabled on the server 2) COR_PROFILER : If profiling is enabled then it checks this value of this env variable to see which profiler its need to load   NET Runtime version 4.0.30319.0 - Loading profiler failed.  COR_PROFILER is set to an invalid CLSID: 'AppDynamics.AgentProfiler'.  HRESULT: 0x800401f3.  Process ID (decimal): 46608.  Message ID: [0x2502]. .NET Runtime version 2.0.50727.8009 - Failed to CoCreate profiler. This error indicates that above-mentioned variables still exist but since you have uninstalled Agent, the 'AppDynamics.AgentProfiler'.dll does not exist. Can you verify if those System level environment variables still exist? If yes can you go ahead and delete them and restart the .Net Application(s). If this does not help a restart of the server might be necessary which will make sure they are removed from registry cache. ... View more