@Sreenivas.Goka  - You can use the github hosted releases from following link - - https://github.com/Appdynamics/DotNetAgentExtensionManager/tree/master/Publish  ... View more

Hi Prashant,  Please run the installer from a command prompt (run as administrator) using the following command line - msiexec /i dotNetAgentSetup64.msi /l*v installlog.txt Let us know if the agent installs fine ? In case if the issue persists, please share complete installlog.txt file as a direct message to me. We will review and update you with next steps. ... View more

Hi Robert, I have written basic steps needed to setup a sample application using linux docker containers.  Instructions for setting up sample environment for using Linux SDK -  Step 1: Getting the Sample Code       mkdir MvcApp       cd MvcApp       dotnet new mvc Step 2: Test the App if it is working fine       dotnet restore      dotnet run      Check in Browser -> http://localhost:5000 Step 3: Add Nuget Package in the Project -  dotnet add package AppDynamics.AgentSDK Step 4: Modify your project to use the AppDynamics SDK -       e.g: Edit HomeController.cs and add following - using AppDynamics;   ...   namespace MvcApp.Controllers   {     public class HomeController : Controller     {     public IActionResult SomePage()     {       var currCtxId = AgentSDK.StartBusinessTransaction("DemoBT", "ASP_DOTNET", "");       // Code here calls to other ASP_DOTNET component         ...       AgentSDK.StopBusinessTransaction(currCtxId);       return View();       }       ... For further reading and usage - https://docs.appdynamics.com/display/PRO45/.NET+Core+for+Linux+SDK+Use+Cases Step 5: Run "dotnet build"  Note: This step should fail with warning-> "AppDynamicsConfig.json : warning APPD001: AppDynamics config was not updated" Step 6: Edit the AppDynamicsConfig.json file with the following information:  {     "controller": {     "host": "<controller_host_name>",     "port": <controller_port_name>,     "account": "<controller_account_name>",     "password": "<controller_account_key>",     "ssl": <true if using https controller, or false>     },     "application": {     "name": "<application_name>",     "tier": "<tier_name>",     "node": "<node_name>"     },     "log": {     "directory": "<log_folder_path, e.g. /tmp/AppDLogs>",     "level": "<log_level, e.g. INFO>"     }  } Step 7: Create Dockerfile under MvcApp folder and Add Following  -     #FROM microsoft/dotnet:2.0-sdk     #FROM microsoft/aspnetcore-build:2.0     FROM microsoft/dotnet:2.0-sdk     COPY . /app     WORKDIR /app     RUN ["dotnet", "restore"]     RUN ["dotnet", "build"]     #RUN ["apt-get","update"]     #RUN ["apt-get", "install", "lsof"]     ENV CORECLR_PROFILER="{57e1aa68-2229-41aa-9931-a6e93bbc64d8}"     ENV CORECLR_ENABLE_PROFILING=1     ENV CORECLR_PROFILER_PATH="/<user,e.g:root>/.nuget/packages/appdynamics.agentsdk/4.5.0/runtimes/linux-x64/native/libappdprofiler.so"     EXPOSE 5000/tcp     ENV ASPNETCORE_URLS http://*:5000     ENTRYPOINT ["dotnet", "run"] Note: For CORECLR_PROFILER_PATH refer the last section on https://docs.appdynamics.com/display/PRO45/Using+.NET+Core+for+Linux+SDK  Step 8: Build the Image (make sure cd MvcApp, if not already the current directory)- docker build -t appdsample:MvcApp . Step 9: Launch the Image - docker run -d -p 8088:5000 -t appdsample:MvcApp Step 10: Apply Load on the application (http://localhost:8088/) and check the reporting in controller and logs under e.g. /tmp/AppDLogs       Doc references  -  https://docs.appdynamics.com/display/PRO45/.NET+Core+for+Linux+SDK https://docs.appdynamics.com/display/PRO45/Using+.NET+Core+for+Linux+SDK https://docs.appdynamics.com/display/PRO45/.NET+Core+for+Linux+SDK+Use+Cases Please follow the instructions to setup the sample environment and do let us know if it works in your environment? Also once verified, please perform needed changes into your original applications setup process and let us know if it works with your application as well or not ?  Thanks, Kartikay ... View more

Hi Prodip,  We have sent direct message to you to share few more details. Please share those details for our review.  Thanks, Kartikay ... View more

We have requested for further details in a direct message to you. Please respond with the details and we will update you accordingly.  ... View more

You can download the existing .net agent version installed on the server from Appdynamics Download site and keep the msi renamed as dotNetAgentSetup64.msi under C:\temp folder and retry uninstallation from control panel.   https://download.appdynamics.com/download/ ... View more

.Net Agent picks all the counters from Windows Perfmon. Based on your requirement you can further configure .Net Agent to collect additional perfmon counters. This is explained in following document - https://docs.appdynamics.com/display/PRO44/Manage+Windows+Performance+Metrics I think what you are looking for is "Free Megabytes" or "% Free Space" counters under "LogicalDisk" category where instance will be C:,D: etc Following is an example on how <machine-agent> section of .net agents config.xml will look like below after you include these counters - <machine-agent> <perf-counters> <perf-counter cat="LogicalDisk" name="Free Megabytes" instance="C:" /> <perf-counter cat="LogicalDisk" name="% Free Space" instance="C:" /> <perf-counter cat="LogicalDisk" name="Free Megabytes" instance="_Total" /> <perf-counter cat="LogicalDisk" name="% Free Space" instance="_Total" /> </perf-counters> </machine-agent> These will show up at Controller UI at Metric Browser at following path or at Individual Node level Application Infrastructure Performance|<Tier Name>|Custom Metrics|.... Note : You will need to restart the Agent Coordinator Service after making any edits to Config.xml. ... View more

Hi Yogesh,  Details steps on how to create data collectors are documented on - https://docs.appdynamics.com/display/PRO44/Data+Collectors Attached screen shot on how to select BTs on which the selected Data Collector is needed to be applied.  After creating the MIDC, do not forget to restart appdynamics agent coordinator service first on the agent machine and then restart the instrumented applications and apply fresh load. Thanks, Kartikay ... View more

Hi Tudor,  We have tested the steps for Installing service fabric as given in - https://docs.appdynamics.com/display/PRO44/Install+AppDynamics+for+Azure+Service+Fabric We were able to make the instrumentation work and here is what we followed - We Manually downloaded the NugetPackage from https://www.nuget.org/api/v2/package/AppDynamics.WindowsAzure/4.4.1 We unzipped it in a folder on the machine.  We copied AppDynamics.Agent.dll, AppDynamics.Profiler_x64.dll, AppDynamicsAgentLog.config, AppDynamicsConfig.json from <nuget_package>\content\AppDynamics and added in the Visual studio solution of each of the Service Project at the top level, not under any folder.  Right Click on each of these 4 newly added files in Visual studio for each service project and make sure under properties Build Action: Content and Copy to Output Directory: Copy Always is selected. Rename AppDynamicsConfig.json to <executable_name>.AppDynamicsConfig.json in each project. Also modify the ServiceManifest.xml in each of the project and add following  -  <CodePackage ...> <EntryPoint> ... </EntryPoint> <EnvironmentVariables> <EnvironmentVariable Name="COR_ENABLE_PROFILING" Value="1" /> <EnvironmentVariable Name="COR_PROFILER" Value="{39AEABC1-56A5-405F-B8E7-C3668490DB4A}" /> <EnvironmentVariable Name="COR_PROFILER_PATH" Value="AppDynamics.Profiler_x64.dll" /> </EnvironmentVariables> </CodePackage> Update the <executable_name>.AppDynamicsConfig.json in each service project, with following  -  { "controller": { "host":"ControllerHost", "port":ControllerPort, "account":"ControllerAccount", "password":"AccessKey" }, "application": { "name":"NameOfTheControllerApplication" } } Publish the Services to the Cluster from Visual Studio, it will publishes the added new files as content of the deployed package. On applying the load on the applications, we started seeing the tiers getting registered for each hosted service in controller. Agent logs were getting created under D:\LogFiles\AppDynamics on the Cluster VMs.  Note: As per your screenshot looks like you have added the nuget package by the package manager in the solution, that is not needed. Which creates a folder Appdynamics in the project and adds all the files in it. The steps shared above is needed to be performed manually after downloading and extracting the nuget package on the machine. Attached screenshot of the my test project which I created for testing the behaviour. ... View more

Hi Denis,  Presently  WebSocket Send and Receive apis are not supported out of the box. However we should be able to define custom match rules for receiving and custom exit points for exit point.  So depending on what APIs you are using you can create custom exit (backend) rule on the class/method to identifiy the exit call.  ... View more

You can utilize AppDynamics .NET extension manager to monitor windows service status.  Please find attached document* to refer to the complete process on how to setup Windows Service status monitoring extension.  Using this extension, configured Windows service status gets reported to Controller as a metric. You can utilize this metric to create alerts on. *In addition to PDF, allso see github hosted releases, below Link ed to additional resources below as well as making minor post-site re-design edits to primarily correct spacing Claudia Landivar, Community Manager & Editorto  ... View more

Hi Sundar,  The embedded machine agent which comes with .net agent periodically collects machine snapshots.  When you recieve alerts for high memory usage, check the time frame and machine it is orginating from and go to Machine Snapshots tab on application dashboard. Filter by machine name and time frame and you would get snapshots with high memory usage.  Review few of these snapshots to identify which of the processes taking high memory. After identifying which process is taking lots of memory, indentify if it is an instrumented .net process or any other process running on the server taking high memory.  For .net based instrumented processes - Check if the process is consistently taking a high memory or if it is increasing with time or if periodically it is going down ?  Based on above details you can pinpoint if there is any memory leak issue or not ? You can also enable object instance tracking for a node to refer top 20 .NET framework classes and the top 20 application classes based upon the number of instances - https://docs.appdynamics.com/display/PRO44/Object+Instance+Tracking+for+.NET In case if the process is showing symptoms of memory leak, you can take memory dump and you can analyse using Microsoft DebugDiag or Win DBG utility.  Important doc links - https://docs.appdynamics.com/display/PRO44/Monitor+Windows+Hardware+Resources - https://docs.appdynamics.com/display/PRO44/Machine+Snapshots+for+.NET - https://docs.appdynamics.com/display/PRO44/Object+Instance+Tracking+for+.NET Thanks, kartikay ... View more

Hi Sundar,  Please find below responses for your questions -  1). In Transaction Snapshots tab, i see some of the transactions are marked as Slow / Very slow . I want to know how App'D detect this as slow transactions because i didn't configure any threshold for this. How its automatically making this happen. ANS:  Please refer following document for better understanding  - https://docs.appdynamics.com/display/PRO44/Transaction+Thresholds#TransactionThresholds-Howisatransactionmarkedslow,veryslow,stall,orerror? https://docs.appdynamics.com/display/PRO44/Transaction+Thresholds 2). Also when we configure Application .(.net agent), we configure BT custom rule and detecting imp. transactions, but after some 1 or 2 days it getting diluted and not showing up. Any remedy for this pls.? ANS: If the configured BTs have continuous load hitting them then you would always see them in BT list In case if you are not seeing them in BT list you could increase the time frame or under Filters options uncheck "Transactions with Performance Data" checkbox and it would start showing all the registered BTs. Out of the box BT list shows all the BTs which are reporting in selected time frame. 3). Is there any limitations on no. of IIS to configure in a single application., I've instrumented some close to 10 IIS in single application, but among that only 5 or 6 are showing up in dashboard. Others are showing some below errors in the log like below  " Warn ConfigurationChannel Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host        exception [System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required." ANS: There is no such limitation. As you are getting (407) Proxy Authentication Required. error it means, there is presence of proxy on the server and to resolve this you can either add controller in the bypass list or add proxy details in agents config.xml as shown below  -  <controller host= "mycontroller.example.com" >    <application name= "MyDotNetApplicaition"   />    <proxy host= "myproxy.example.com"   port= "3128"   enabled= "true" >       <authentication enabled= "true"   user_name= "MyProxyUser"   password= "password"   domain= "mydomain.com" />    </proxy> </controller> https://docs.appdynamics.com/display/PRO44/.NET+Agent+Configuration+Properties Thanks, Kartikay ... View more

Hi Sundar,  Please follow the steps shared by Gurmit and let us know if face any issues.  In case if you still face the issue - * Please share screen shot of the list of BTs getting identified and also highlight the section which is problematic. * Please let us know if the instrumented application is ASP.Net based or you have configured custom match rule ?  * Please share screenshot the rules which you created for those 4 BTs for our review.  ... View more

Hi abantly,  We have reviewed the shared details and we do not see the exit call from the upstream application. We have requested some details in the private message we have sent.  Please provide those details and we will look into possible solution.  ... View more

Hi Indrajit,  We have URL Monitoring extension  - https://www.appdynamics.com/community/exchange/extension/url-monitoring-extension/ It is an extension for Java Machine agent for more details on java machine agent refer - https://docs.appdynamics.com/display/PRO43/Standalone+Machine+Agent Let us know if that suits your requirement.  ... View more

The issue could be either related to network related or the service itself is taking longer time to respond. The first step would be to identify where the bottle necks is ? For example, use WireShark to see if the connection establishment is taking a long time.  As it is WCF service, you can turn on WCF trace logs on the server.  Refer - http://msdn.microsoft.com/en-us/library/ms751526.aspx WCF traces will give you details on what is happening on service side and is there any issue happening there.  ... View more

Thanks for for the update Andreas. Good to know that issue is resolved. ... View more

Hi Harshad,  Good to know that the issue is resolved. Thanks, kartikay ... View more

Hi Harshad,  I am assuming that you are using Unattended+Installation+for+.NET.        https://docs.appdynamics.com/display/PRO42/Unattended+Installation+for+.NET If above is correct then you just need to add following in the end of the batch file used to install the .net agent - iisreset Let me know if above helps ? ... View more