Discussion Feed

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    Dario,    Can you please share the VSTS pipeline output in .txt format. We are not able to see complete details on what is happening in each step.    Also please share complete value of the environment variables you have added in your local project for our review. We will review them and accordingly update you.    Also under AppDynamicsAgentLog.config file check following directory and if you have some logs, please share them to me as direct message.    ${environment:variable=HOME}\LogFiles\AppDynamics   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

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

Hi Supadhyaya,    We have sent you direct message with further details on debugging the issue. Please refer it and we will update you as per the instructions in the message.   Thanks, kartikay ... 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