Hi @Esko.Jaakkola  @Paul.Mateos    When you invoke the WCF service call from any of the parent applications ( or UPStream ), this invoked WCF service call will be a part of the BT only, you will not see any of the new BT registered. InCase, there is no instrumented UPStream application is present and you are  directly instrumenting and calling the WCF service URL, so in this case, you would see the BT related to the downstream WCF service ( OOTB discovery) Regarding the BT discovery part: As you are seeing the BT name as "RESTService.JSONrequest", it points that the service name is RESTService and the Method name is "JSONrequest" Currently, for WCF there is no Split condition available you can only configure with the multiple match condition on the service name as well as the Method name. Could you please help us with the exact use case are looking for For example  1. Different BT registration based on each different WCF URLs 2. Snapshot for each of the WCF URLs execution separately  OR 3. would like to see the count of each WCF service URL invoked. For Example Count of -> https://utu-ht.tulli.fi/utufrontend/RESTService.svc/IB400A  Count of  -> https://utu-ht.tulli.fi/utufrontend/RESTService.svc/IB400B    Thanks, Ashish.   ... View more

Hi Tamir,   If we understand, you have two server name one is like "server01" and another is like "server01-java-MA". The Controller UI might show the server name with "-java-MA" appended to the host ID. This is expected behavior; the "-java-MA" suffix indicates that the host has a Standalone Machine Agent running in .NET Compatibility Mode.  For more details, please refer to the below document. https://docs.appdynamics.com/display/PRO45/.NET+Compatibility+Mode Let us know if it helps. Thanks, Ashish. ... View more

Hi  Michael,   Could you please review the below document, and let us know if it helps.   "When you enable object instance tracking for a node, AppDynamics analyzes the heap to identify classes with the most instances on the heap. AppDynamics tracks the top 20 .NET framework classes and the top 20 application classes based upon the number of instances. Use object instance tracking to identify memory usage trends in classes with large numbers of instances." For more details please review the below document. https://docs.appdynamics.com/display/PRO45/Object+Instance+Tracking+for+.NET Thanks, Ashish. ... View more

Hi Ahmed, We notice that you have already raised a ticket with us with number #217116 and our team is already working on this. We will further do followups to this issue on the ticket which you have raised with us. Thanks, Ashish. ... View more

Hi Doug, As per our precious AppDynamics documents, it seems for the Config Management requirement was ".NET Agent 4.1 or later installed on machines where you plan to deploy configuration." So, it looks like this Config Management for .NET feature was present from .Net Agent version 4.1.X. For reference, you can refer to the below document [ It is 4.1.x version related document ] https://docs.appdynamics.com/display/PRO41/Manage+Configuration+for+.NET Please let us know if it helps, or you have any further questions. Thanks, Ashish. ... View more

Yes Pauric, you would need to install the ,NET Microservice Agent on each on the .NET Core applications which you want to instrument.  Thanks, Ashish. ... View more

Hi Narasimha,   If application is a .NET 4.5 framework based MVC API running on the windows VM, then we do not have any NuGet package specific for the solution, To instrument this kind of application, you would need to use the .NET msi based agent installer.   If you have applications, those are based on .NET Core 2.0 or above and running on windows VM, then to instrument these applications you can use the .NET Core microservice agent for windows NuGet package.    Let us know if it helps or you have any further questions.   Thanks, Ashish. ... View more

Hi Doug, Currently, for .Net applications, which are instrumented with the .NET msi based agent and use the cofig.xml file, we can use the  Config Management tool in the AppDynamics Controller to upload and manage .NET Agent config.xml files. It will help to assign configurations to machines where the .NET Agent is running at a time. You can refer to the below document - https://docs.appdynamics.com/display/PRO45/Manage+Configuration+for+.NET Let us know if you ave any question. Thanks, Ashish. ... View more

Hi Sandy,   As the document says - The .NET Agent Coordinator Service must be the same architecture as the monitored application. For example, a 64-bit coordinator with a 64-bit IIS application. As per logic and implementation, you should always install the .NET agent match with OS bitness. Now,  in your case you have 64 bit Windows OS, so you would need to install the 64 bit .NET agent. But to enable object instance tracking, NET Agent Coordinator Service must be the same architecture as the monitored application, here in your case both are different. So, in the shared scenario, object instance tracking will not work. Thanks, Ashish. ... View more

Hi Yann, It seems like you are trying to monitor the Microsoft Exchange Windows services on the Windows Server 2012. We are not sure whether these services are .Net components. If they are .Net processes then you can use the AppDynamics .Net Agent to configure them. However, the best way is to check to see if these services are .net components is by running the following command tasklist /m "mscor*". The output of the above command lists the processes that have DLLs starting with mscor*, indicative of .NET processes. Processes that are not on the list are not .NET processes and cannot be instrumented with the .NET Agent. Please refer to the following document link for more details  - https://docs.appdynamics.com/display/PRO45/Configure+the+.NET+Agent+for+Windows+Services+and+Standalone+Applications Please let us know if you have any further questions. Thanks, Ashish. ... View more

Hi Prakash, The HTTP data collectors allow you to capture the request http headers as we intercept the incoming requests. So for capturing any data related to response, you would need to define the Method invocation data collectors on any method which is having visibility to the response headers. https://docs.appdynamics.com/display/PRO45/Data+Collectors Let us know if you have any question. Thanks, Ashish. ... View more

Hi Esko, By default, the AppDynamics auto-detection naming scheme identifies all WCF transactions using the service name and operation name:  ServiceName.OperationName For example, a web service for a travel website books reservations from client front ends: "TravelService.BookTravel". For more details, you can refer to the below section and document Automatic Naming for WCF Transactions https://docs.appdynamics.com/display/PRO45/WCF+Entry+Points From the following details "Problem is that all wcf calls are displayed under two or three call like RESTService.JsonRequest()".Looks like RESTService is a service name and JsonRequest is a method name and from the following sentence "there is a lot of calls with different URL", Are you trying to access or invoking this WCF service from different asp.net applications URL? If yes, do you see the different BTs for those application's URL and Exit call? OR, there are different -2 WCF URLs in which you have the same Service name and Method name? Could you please confirm. Also, if you do not want to identify service as WCF service and want to identify as an asp.net URL and transaction, you can disable the WCF Transaction Monitoring Enabled and Discover Transactions automatically for WCF requests. For reference see the attached screenshot. Let us know if you have any question. Thanks, Ashish. ... View more

Hi Priyank, Have you restarted the Agent Coordinator service and then standalone application service in a sequence after configuring the standalone app in configuration filel?  Do you see the coordinator service process and application service process entry in the agent log file ? Please provide read and write permissions to account under which the executable is running at DotNetAgent folder ( Logs  directory ) and <AppDynamics_Agent_InstallationDirectory>\AppDynamics folder and then restart both Agent Coordinator and the application service. After that apply the load on the application and then check teh behaviour. Let us know if it helps or you have any question. Thanks, Ashish. ... View more

Hi Prashant, Could you please provide us the complete Agent installtion log file for our review on the SFTP location which i have sent you  in a private message. Also, we request you to please create a seprate post for the issue that you are faccing with java agent, machine agent. It will help us to trake the issue better. Thanks, Ashish. ... View more

Hi Michael, If we understood correcrly from the shared details, after the matinece agent is not reporting the data metrics for the instrumented application. To troubleshoot the issue further, could you login to this agent machine after that kindly restart the Agent coordinator service  and then restart the IIS in the given sequence. After that applied the load on the instrumented application and then check the behaviour. Let us know if it helps. Thanks, Ashish. ... View more

Hi Dynis, If we understood correctly from the shared details, application configured under the "RTIS_Standalone" Tier is getting freeze from 2 to 5 minutes for every 2 hours and then it works fine witout any issue. Could you verify and confirm -  Do you see this hung situation during any specific BT execution or all BT execution ? Is this issue occuring randomly or you can reproduce this issue on demand basis ? Kindly provide us the latest zip of complete DotNetAgent folder located at %ProgramData%\AppDynamics for our review in the the SFTP location, which i just shared with you in private message. Thanks, Ashish. ... View more

Hi Alberto, After successful installation of .Net Agent, Have you restarted the  "AppDynamics.Agent.Coordinator_service first and then IIS/instrumented application service in sequence? If not, kindly restart services in the given sequence and after that apply the load on the applications. Let us know if it helps or you are still facing the issue. Thanks, Ashish. ... View more

Thanks Abhinav for the update.   In the document ( https://docs.appdynamics.com/display/PRO44/Install+the+.NET+Core+Microservices+Agent+for+Windows), the suggested Environment variables are for the System level. So there we need to provide the complete path.  But when we configure these Environment variables at the specific application level and configure through web.config file. We can also give the relative path as suggested. it will also work. We will share the suggestion with the document team to update this information. Thanks, Ashish. ... View more