Discussion Feed

Hi Durga,   In the provided information, we are not clear about the root cause of the issue. Can you please create a support case and provide all the requested details at help@appdynamics.com.   Thanks, Venu. ... View more

Hi Soundarajan,   Creating the POCO rules for the registered windows service, please refer to the following document link https://docs.appdynamics.com/display/PRO44/POCO+Entry+Points   For the second issue, please check if the  FSASService.exe application takes the following command line "-x" as input. If not then please remove it and then restart the application and check if the tier is getting registered for this application.     Thanks, Venu. ... View more

Hi Soundarajan,   It seems like there is no continuous traffic on your application. If there is no traffic on your application then the Agent won't report any metrics.    Thanks, Venu. ... View more

Hi Kiran,   Sorry for the latest response.   If you are still facing the same issue then please provide us the below details to investigate this issue further.   Upload the latest zip of DotNetAgent folder to the following location https://appdynamics.egnyte.com/ul/2TVrdOrMls Screen capture of the Test Controller connection from the AppDynamics Agent Configuration wizard. Screen capture of the Telnet <Controller Host> <Port> command output Screen capture of the Internet Explorer browing the Controller from the problematic Agent server. Screen capture of the  tracert <Controller Host> command. Thanks, Venu. ... View more

Hi Maheswar,   I mentioned in my previous post the issue  is resolved in the 4.4.1 .Net Agent version. It is not related to .Net Framework version. Seems you have used the .net framework version 4.5.2  to build your instrumented application.   Could you please install the latest available 4.4.x Agent version on the agent machine and then check the behaviour.   Let us know if you have any question.   Thanks, Ashish. ... View more

Thankyou Raunak for your reply.   Actually may be I was not able to keep my question properly.   What I menat or what i want to ask is that :   1. Can we able to create multiple application for same IIS ?? for example : I have created 2 Application(Appdynamics application) one is Finance and another is HR Now I am creating Tiers of the Finance and assigning the nodes to tiers of Finance and completed the setup for the same. Now I am creating Tiers of the HR and assigning the nodes to tiers of HR and completed the setup.   Please note I have created and assiginged Application and tiers and nodes in the same IIS server as my sites are hosted in one server not in two diffrent server and agent is also installed in the same server. that means for Finance and HR the AppDynamics App name is diffrent and so do the tiers and assigned nodes.     What actually happening wit me is that when i am assinging tiers and nodes for Finance and complete the setup and created the HR and assigned the Nodes to tiers i can see the from UI that both HR and Finance tiers and nodes are reporting in HR, when i check the config.xml i can see only HR apllication only and all the Tiers and Nodes are under that application only, what i want is to seperate Finance and HR as the tiers i created and assigined to them are diffrent and they should report to their respective AppDynamics App.   Please see the screenshot: issue while creating new Application in exesting IIS     Regards, Shah, Indrajit Kumar                 ... View more

Hi Indrajit,   It seems like you are referring to the Agent Configuration wizard tiers list. The Agent will get those tier names from the Controller  and will display in the list. So, you can simply ignore those tiers in the wizard and complete all the steps. Once you complete the wizard, it updates the config.xml file with the only tiers that you selected to instrument.    Once the above step is done and the once Agent started reporting the metrics to the configured tiers, you can logon to the Controller UI and delete unused tiers manually by right clicking on the tier name.     Thanks, Venu. ... View more

Hi  Soundarajan,   Please see my inline comments to your quries.   In above snapshot (mark 1), 12.8 S (1 call) is this time taken by that node RMGPortal to make any outgoing call or it’s a call to that node itself? Ans --> Yes, the 12.8 sec is the avg. response time taken for that 1 call which executed at the RMGPortal tier. (Mark 2) 20.3 Seconds I believe that’s time took for a call from node RMG Portal to Authorisation web service. Pls correct me if I’m wrong. Ans --> Yes, the 20.3 sec is the avg. response time taken for the Web Service exit call from the RMGPortal tier. Same like in (mark 3) it shows 200 MS & 8 Calls , could someone tell what’s that denotes .? Ans --> Here, the 200 ms is the avg. response time for the 8 calls executed at the AuthorizationWebService tier. Thanks, Venu. ... View more