Showing results for 
Show  only  | Search instead for 
Did you mean: 

Monitoring a stand-alone C# .NET application




Ive a controller and a single .Net Agent - to moniter a standalone .Net exe - Ive followed the .Net Agent config wizard (given the Name and Account Key - in the config file at C:\Program

Files\AppDynamics\AppDynamics .NET Agent\Config\config.xml).

The agent shows up in the controller GUI - under the "Tiers & Node" section - but I also see a lot of warnings in the top right corner of the controller GUI:


Agent license request denied. Agent type: ; Host: machinename; Reason: Not licensed for controller


Also , in the controller GUI - is there any place I can see the agent profile logs - ie where can I see the output of the profiling being done of the standalone app - can you please let me know,



Hi ,

I'd reached out to sales and received a new LIC file - which I'd placed as per instructions it worked now.


Ive now one .Net agent - monitering a standalone .Net exe. I see the .Net agent profiling the exe - thrugh the logs at C:\Program Files\AppDynamics\AppDynamics .NET Agent\Logs\Profiler - but I dont see any such info on the controller GUI - as business transactions or profileing information about the exe Im trying to profile.


Can you please suggest how can I see those logs/events/business transactions in my GUI (about by .Net Agent monitering standalone .Net exe)


AppDynamics Team (Retired)

The following guide explains how AppDynamics detects Business Transactions and what you can do if AppDynamics doesn't recognize your application's Business Transactions out of the box.


How does AppDynamics detect new Business Transactions?


AppDynamics detects new Business Transactions by recognizing a particular set of "entry" methods in the callstack of the executing application. When one of these methods is hit, a new Business Transaction starts and all methods executing downstream of this method are instrumented.


No Business Transactions were detected in my application, now what?


In cases where no recognized Business Transaction entry methods are hit, we can enable the agent node property named find-entry-points to find some. With find-entry-points enabled, AppDynamics will log a call stack to BusinessTransaction.logeach time a recognized outgoing call is made. For example, any HTTP/ASMX/WCF/Remoting service, DB, or MQ call. You can find the BusinessTransactions.log in the agent logs folder.


We can then review these callstacks to determine which method will make a suitable "entry" point to begin a Business Transaction.


Callstack example shows what code is running in the application


The following callstack is an example of what we might find in the BusinessTransactions.log after enabling find-entry-points. It should be read from the bottom up. That is, methods furthest down executed first. Look for callstacks following Thread Empty_Name >> which means they are not part of any existing BT.


... BusinessTransactions Logging request stack for Thread Empty_Name >>
System.Data.SqlClient.ExecuteReader() <---AppDynamics recognized this as an exit and logged the callstack.


We can see that this is a Windows Forms application where a particular button was clicked to find customer data. Once that button was clicked, an outgoing database call was made which AppDynamics recognized. From this point, AppDynaimcs code was executed to log the callstack to the BusinessTransaction.log file.


Which application method would make a good Business Transaction entry point?


Remember, methods executed first are at the bottom of the callstack. Looking at methods that executed before the database call, we can see that MyCompany.MyClass.UI.btnFindCustomerData_OnClick() is a custom developed code that would make a suitable starting point for this unique Business Transaction to begin. All methods which execute after this method are also tracked as part of this Business Transaction. If we use a method that executed before this one, for instance System.Windows.Forms.Button.OnClick(), every application button click would be tracked as part of the same business transaction, which is not ideal for troubleshooting. We want to make sure separate code paths are tracked as separate Business Transactions.


OK I've found a suitable Business Transaction entry point method, now what?


Once we've found a suitable BT entry point, we can configure a .NET Class/Method Custom Match Rule to let AppDynamics know that this method marks the start of a new Business Transaction. Once you've created the Custom Match Rule, you'll need to wait a minute or two for the rule to be brought down to the agent, then restart the application for the change to go into effect. Once in effect, you should see your Business Transaction show up in the controller.


Just let us know if you have any further questions regarding this.



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.