Discussion Feed

Ashish.Singh

Hi Will, AppDynamics .Net Agent does not instrument classic ASP websites. It only instruments the applications built on .Net framework version 2.0 and above or in other words managed code running on .NET version 2.0 or greater. Please refer to the following document link for the supported framework details. https://docs.appdynamics.com/display/PRO45/.NET+Supported+Environments You can try to use the EUM for monitoring the end user experience via browser, As Classical ASP website contains a markup for making HTML so in the end, we are just running an HTML page with JS on it. You can try the Manual injecttion as per the document below - https://docs.appdynamics.com/display/PRO43/Manual+Injection For related to EUM monitoring, you can refer the below document. https://docs.appdynamics.com/display/PRO43/End-User+Monitoring If it doesn’t work or you face any issue, you can raise a new ticket with EUM support. our EUM SME will help you on this. Thanks, Ashish.

Ashish.Singh · ‎11-23-2018

Hi Ankit, For further troubleshooting, we sent a private message to you for to upload the required details in the SFTP location. Could you please upload the details and confirm here. We will review the details and update you. Thanks, Ashish.

Ashish.Singh · ‎10-26-2018

Hi Priyank, Have you restarted the Agent Coordinator service and then standalone application service in a sequence after configuring the standalone app in configuration filel? Do you see the coordinator service process and application service process entry in the agent log file ? Please provide read and write permissions to account under which the executable is running at DotNetAgent folder ( Logs directory ) and <AppDynamics_Agent_InstallationDirectory>\AppDynamics folder and then restart both Agent Coordinator and the application service. After that apply the load on the application and then check teh behaviour. Let us know if it helps or you have any question. Thanks, Ashish.

Ashish.Singh · ‎09-25-2018

Hi Prashant, Could you please provide us the complete Agent installtion log file for our review on the SFTP location which i have sent you in a private message. Also, we request you to please create a seprate post for the issue that you are faccing with java agent, machine agent. It will help us to trake the issue better. Thanks, Ashish.

Raunak.Mohanty · ‎09-17-2018

@Viet.Nguyen we have shared the internal enhancement requests via support case.

Ashish.Singh · ‎09-11-2018

Hi Michael, If we understood correcrly from the shared details, after the matinece agent is not reporting the data metrics for the instrumented application. To troubleshoot the issue further, could you login to this agent machine after that kindly restart the Agent coordinator service and then restart the IIS in the given sequence. After that applied the load on the instrumented application and then check the behaviour. Let us know if it helps. Thanks, Ashish.

Ashish.Singh · ‎09-07-2018

Hi Dynis, If we understood correctly from the shared details, application configured under the "RTIS_Standalone" Tier is getting freeze from 2 to 5 minutes for every 2 hours and then it works fine witout any issue. Could you verify and confirm - Do you see this hung situation during any specific BT execution or all BT execution ? Is this issue occuring randomly or you can reproduce this issue on demand basis ? Kindly provide us the latest zip of complete DotNetAgent folder located at %ProgramData%\AppDynamics for our review in the the SFTP location, which i just shared with you in private message. Thanks, Ashish.

Ashish.Singh · ‎08-28-2018

Hi Alberto, After successful installation of .Net Agent, Have you restarted the " AppDynamics.Agent.Coordinator_service first and then IIS/instrumented application service in sequence? If not, kindly restart services in the given sequence and after that apply the load on the applications. Let us know if it helps or you are still facing the issue. Thanks, Ashish.

Ashish.Singh · ‎07-06-2018

Thanks Abhinav for the update. In the document ( https://docs.appdynamics.com/display/PRO44/Install+the+.NET+Core+Microservices+Agent+for+Windows), the suggested Environment variables are for the System level. So there we need to provide the complete path. But when we configure these Environment variables at the specific application level and configure through web.config file. We can also give the relative path as suggested. it will also work. We will share the suggestion with the document team to update this information. Thanks, Ashish.

Venu Babu.Thangallapelli · ‎06-25-2018

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.

Date Registered	‎07-07-2016 09:45 AM
Date Last Visited	Friday
Total Messages Posted	56
Total Kudos Received	9

Discussion Feed

Re: Classic ASP support agent

Re: Appdyamics not capturing events for .NET appli...

Re: Agent disabling itself

Re: Installing .net agent on Windows 10. Getting E...

Re: Remediation Script on Windows Node

Re: .NET application not reflecting any data on da...

Re: AppDynamics and .Net Standalone apps

Re: Configured .Net agent not reporting to control...

Re: Environment Variable and Path for Self Contain...

Re: .Net agent connectivity issue