Discussion Feed

Hi Soundrajan,   Windows service will run a standalone executable internally, so you we recommended you to replace the windows service section with that of stand alone one. Windows service section was used with older agents. For latest agent we recommend you to use stand alone configuration.   Please let us know if that does not help.   Regards, Ashutosh ... View more

Hi Soundrajan,   Instead of using windows service configuration, please configure the exectable running behing as stand alone application, as mentioned in following document.   https://docs.appdynamics.com/display/PRO43/Configure+the+.NET+Agent+for+Windows+Services+and+Standalone+Applications   You configuration should look like below: <?xml version="1.0" encoding="utf-8"?> <appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <controller host="mycontroller.mycompany.com" port="8090" ssl="false"> <application name="My Business Application" /> </controller> <machine-agent /> <app-agents> <IIS> <applications /> </IIS> <standalone-applications> <standalone-application executable="MyWindowsService.exe"> <tier name="Windows Service Tier" /> </standalone-application> <standalone-application executable="MyStandaloneApp.exe"> <tier name="Standalone Tier" /> </standalone-application> </standalone-applications> </app-agents> </appdynamics-agent> After modifying the config.xml, please restart the coordinator service and windows application sequentially and then apply the load. Once you can see your node registered, you need to create POCO entry points for business transactions as mentioned in document below:   https://docs.appdynamics.com/display/PRO43/POCO+Entry+Points   Regards, Ashutosh ... View more

Hi,   Following message will be logged by .Net runtime when it sees a process not to be instrumented by profiler.   NET Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: 'AppDynamics.AgentProfiler'. Process ID (decimal): 6196. Message ID: [0x2516].   This message is harmless and you can safely ignore it. Please let us know if you are facing any issue with .Net agent where an instrumeneted application is facing some issue.   Regards, Ashutosh ... View more

HI Irhazi,   Apologies for late response as I was having technical issues with my laptop from couple of days.   Please upload the latest Event logs and DotNetAgent folder in the upload link provided to you. I dont see any data there as of now.   Regards, Ashutosh ... View more

Hi Irhazi,   From the event logs we see following .Net error:   .NET Runtime version 4.0.30319.34014 - Loading profiler failed. COR_PROFILER is set to an invalid CLSID: 'AppDynamics.AgentProfiler'. HRESULT: 0x800401f3. Process ID (decimal): 5756. Message ID: [0x2502]. This occurs when installation/uninstallation in not propeper and mentioned environment variable is not available correctly. Please stop your IIS and uninstall the agent. Once uninstallation is complete Please check the system level environment variables if following 2 variables are still present. COR_ENABLE_PROFILING COR_PROFILER If these are present, please delete the values for these variables. Also, please cheche your global assembly cache(GAC), if there are AppDynamics dlls present even after uninstalling the .Net agent. If dlls are present, please remove them from there manually. To open GAC: Run-->assembly After proper removal of agent. Start your IIS and run the AppDynamics installer with admin privillage. After installation, it will open the wizard so please follow the instruction on the wizard and reach till the end(allow this is to restart coordinator service and IIS). If you still see the issue, please upload DotNetAgent folder and event logs, at the same repository.   Regards, Ashutosh       ... View more

Hi Irhazi,   We have shared an upload link through a private message. Please use the link provided to share the requested data.   Regards, Ashutosh ... View more

Hi Irhazi,   It seems your instrumentaed process is crashing when monitoring starts. Please let us know if you have access to zendesk. If you have access, please open a support ticket as it will be better to track the issue there.   Regards, Ashutosh   Regards ... View more

Hi,   Please attach your DotNetAgent folder along with the screen shot of application structure (website and application level). We need to understand the hosting structure of the application.   Regards, Ashutosh ... View more

Hi,   From the image, we can see an incoming call to your  datawarehouse(which we assume is the IIS hosted application). As you mentioned that you are able to see the url of WCF service which is answering your ESB client applications, please update us some more information around this. What kind of application(JAVA, .Net etc) is this which makes call through web service, to dataware house? Do you host any of the web service at your datawarehouse process(IIS hosted applications), which you expect to serve ESB's question? We guess you have all WCF services only, hosted at the IIS. If application hosted at datawarehouse are of WCF type, then calls visible as WCF are being shown as expected. If this is not the case, please help us to understand the ties which hosts web service and please share the WSDL of that(this will help us to understand the url and method names). Regarding your question about the class and method name serving the ESB questions, you can enable find-entry-points property of associated tier and this will dump the call stack of the BT. You can see the class/method names from there. To enable the find entry points property please follow the steps mentioned below: 1. Go the the "Tiers & Nodes" and select the specific tier. 2. Right corner we can see the "Actions ", click on it. 3. Now you can find "Configure App Server Agent", click on it. 4. Select "Use Custom Configuration" . 5. Search find-entry-points property and set the value as True. After this save the configuration. Regards, Ashutosh ... View more

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 ... View more