Hi Sandeeo,
To instrument stand alone applications, you need to create custom entry points for the applications in case your application is not using any OOTB(Out of the Box) instrumentors. You can refer to following document.
https://docs.appdynamics.com/display/PRO42/Instrument+Windows+Services+and+Standalone+Applications
As you mentioned that you are not seeing the servers under tier and nodes, please check if servers are listed under machine agent tietrs.
If you do not have information about class name and method name that you can use to create POCO entry point. You can use "find-entry-points" node level proprty to dump the call stacks for calls(assuming you are making some exit call). Please refer the document below for details around this property.
https://docs.appdynamics.com/display/PRO42/App+Agent+Node+Properties+Reference#AppAgentNodePropertie...
https://docs.appdynamics.com/display/PRO42/App+Agent+Node+Properties#AppAgentNodeProperties-editregi...
Following guide will help you to instrument the stand alone application.
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 callstack to the BusinessTransaction.log each 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 >>AppDynamics.Agent.ManagedAPI.ps.kkAppDynamics.Agent.Interceptors.ww.jvAppDynamics.Agent.MethodExecutionEnv.MethodBeginSystem.Data.SqlClient.ExecuteReader() <---AppDynamics recognized this as an exit and logged the callstack.MyCompany.MyClass.DataAccess.FindCustomerData()MyCompany.MyClass.BusinessLogic.TransformCustomerData()MyCompany.MyClass.UI.btnFindCustomerData_OnClick()System.Windows.Forms.Button.OnClick()System.Windows.Form.ButtonBase.WindProc(...)System.Windows.Forms.NativeWindow.Callback(...)
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 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.
Regards,
Ashutosh
