Skip to main content

Integrating AppDynamics with core

AppDynamics provide information about your application/server at single place. Application performance, integration with other systems, business transactions,  user load and exceptions, AppDynamics provide all these information under one dashboard.
Integrating AppDynamics with core is very simple. Here are the steps to integrate it with your core application.

1. Download AppDynamics agent libraries from AppDynamics Download Center
2. Extract it on Linux machine and copy the extracted files in your website folder. These are the extracted files - 
  • AppDynamics.Agent.netstandard.dll
  • AppDynamicsConfig.json.template
3. Rename 'AppDynamicsConfig.json.template' to 'AppDynamicsConfig.json'
4. Make the required changes as per your AppDynamics Controller setup (assuming your AppDynamics Controller is already setup and running)

If you are using .json file, please include below lines in your AppDynamicsConfig.json file
"feature": [
Read AppDynamic documentation for more details. 
5. Setup few mandatory environment variables on Linux machine
Environment Variable Name Value
CORECLR_PROFILER {57e1aa68-2229-41aa-9931-a6e93bbc64d8}
CORECLR_PROFILER_PATH Path to the libappdprofilerdynamic library. For example, /

Note: Command to setup environment variable on Linux - 
Command to check environment variable on Linux - 
linux-machine# echo $CORECLR_ENABLE_PROFILING

All set to verify your snapshots on AppDynamics controller. Open AppDynamics Controller or Dashboard and verify your application is visible on dashboard


Popular posts from this blog

Cannot alter the login 'sa', because it does not exist or you do not have permission.

Working on projects, it can happen that 'sa' account gets locked. If it is on local machine OR development boxes, onus would be on you to fix it. If scripts and SQL steps are not working, this might help you fixing the issue. Steps to unlock 'sa' account and resetting the password. 1. Open SQL Server Configuration Manager 2. Select SQL Server Services -> 'SQL Server' service. 3. Right click on 'SQL Server' service and click on "Startup Parameters". For 2008, server "Startup Parameters" are inside Advanced tab.   4. Add '-m' in startup parameters as shown above and click on 'Add'. This will put SQL server into 'Single User Mode' and local admin will have 'Super User' rights. For 2008, server you have to add ':-m' in the last of the existing query. 5. Save the settings and Restart the service. 6. Now open the SQL Server Management Studio and connect to database using 'Windows A

Could not load file or assembly 'Microsoft.Web.Infrastructure'

Could not load file or assembly 'Microsoft.Web.Infrastructure, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. What 'Micorosoft.Web.Infrastructure' does? This dll lets HTTP modules register at run time. Solution to above problem: Copy 'Micorosoft.Web.Infrastructure' dll in bin folder of your project and this problem should be resolved. If you have .Net framework installed on machine, this dll should be present on it. You can search for this dll and copy it in your active project folder.   Alternatively,  you can install this dll using nuget package manager PM> Install-Package Microsoft.Web.Infrastructure -Version 1.0.0 Happy coding!!

Git merge from one repo to another repo

This blog is for those who are looking for merging code from one repo to another repo. Why I will merge code from one repo to another? I forked from one git repo( may be some public git repo ) and did some cutomization on existing code. Occasionaly, features are being introduced in main git branch and I would like to get all those features in my own git repo. In this scenario, I would like to merge latest changes in my git repo. Here are few simple steps which will merge code from one git repo to another- 1. Clone the repo1(source git repo) > git clone   > git pull 2. Clone the repo2(destination git repo) > git clone > git pull 3. Goto repo2 (destination git folder) and checkout your prefered branch > cd repo2 > git checkout master>  4. Use below command to see the remote branch associated with your destination git repo > git remote -v  origin