Discussion Feed

Hi  joris ,   Thanks for the update.   If i understand correctly, Currently, you have performed the below steps -  You have deleted the Staging environment WebRole first Then, you have un-installed the previous version of agent nuget package and installed the latest azure 4.3 aganet version package again on the solution and deployed the webrole. Then, after the deployment you have restarted the webRole application from the azure portal. But still you are not able to see the metrics on the controller UI.   To troubleshoot further, please provide us the below details -  What is the .Net framework, you have used in your instrumented .net application. Please login to the WebRole VM and run the below tasklist command using command prompt with admin run as administrator. and provide us the output in private email. tasklist /m "mscor*" tasklist /m Appd* tasklist /FI "IMAGENAME eq w3wp.exe" /m Do, you have continuous load on the application or not. If not, please apply the continuous load on the application and check the behaviour.   Please let us know, if you have question.   Thanks, Ashish.   ... View more

Hi joris ,   Thanks for providing the requested details.   From the provided logs, we observe that .net machine agent has reistered but we do not see any log entry for running worker process. Seems agent is not able to hook into the worker process and due to that apprlication process is not instrumented. We also see some connectivity issue in the logs.   To troubleshoot this issue further, could you please provide us the below details-   From the logs, we see you have upgraded the .net agent from 4.2.15 to 4.3.3. As you are installing the agent through Nuget packege, have you uninstalled previous agent nuget package first before installing this new latest Nuget packege ? Please verify and confirm. After installing nuget packge on solution and delpoying the agent on the azure instance, have you restarted the WebRole application? If not, please restart the WebRole/Worker role application and then apply the continus load on the application and check the behaviour. For verifying the connectivity issue, Could you please perform the telnet the controller on specified port by using following command:   telnet <controller name> <port>   and update us the result. Also, please browse the controller URL on the agent box using the IE browser and confirm you are able to browse that ? Please let us know, if it helps or you have any question.   Thanks, Ashish. ... View more

Hi Sundarapandian, Please find the answers below- 1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection? Answer -> If i understand correctly, you are referring here the performance overhead after creating the Http data collector and MIDC ? If yes, Http data collector is invoked whenever there is snapshot captured. Adding http data collector, add some negligible overhead. However if the frequency of snapshot is high than normal rate then application might have some overhead.So,it is calculated based on frequency of snapshot. And when you create MIDC, The overhead depends on the ByteCode instrumentation. If the instrumentation is happening on short running methods then it will add negligible overhead for each execution.So, based on your MIDC definitions the overhead will be calculated. 2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point? Answer -> If you are making call to mainframe services over HTTP or SOAP protocol then .Net agent is able to detect the exit call OOTB and if you are making call to mainframe services over Socket then we need to do the some custom configuration to detect the exit call. Please let us know, if you have any question. Thanks, Ashish. ... View more

Hi Sundarapandian,   Please find the answers below-   1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection?     Answer -> If i understand correctly, you are referring here the performance overhead after creating the Http data collector and MIDC ? If yes, Http data collector is invoked whenever there is snapshot captured. Adding http data collector, add some negligible overhead. However if the frequency of snapshot is high than normal rate then application might have some overhead.So,it is calculated based on frequency of snapshot. And when you create MIDC, The overhead depends on the ByteCode instrumentation. If the instrumentation is happening on short running methods then it will add negligible overhead for each execution.So, based on your MIDC definitions the overhead will be calculated.   2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point?    Answer -> If you are making call to mainframe services over HTTP or SOAP protocol then .Net agent is able to detect the exit call OOTB and if you are making call to mainframe services over Socket then we need to do the some custom configuration to detect the exit call.   Please let us know, if you have any question.   Thanks, Ashish. ... View more

Hi Sundarapandian,   Please find the answers below-   1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection?     Answer -> If i understand correctly, you are referring here the performance overhead after creating the Http data collector and MIDC ? If yes, Http data collector is invoked whenever there is snapshot captured. Adding http data collector, add some negligible overhead. However if the frequency of snapshot is high than normal rate then application might have some overhead.So,it is calculated based on frequency of snapshot. And when you create MIDC, The overhead depends on the ByteCode instrumentation. If the instrumentation is happening on short running methods then it will add negligible overhead for each execution.So, based on your MIDC definitions the overhead will be calculated.   2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point?    Answer -> If you are making call to mainframe services over HTTP or SOAP protocol then .Net agent is able to detect the exit call OOTB and if you are making call to mainframe services over Socket then we need to do the some custom configuration to detect the exit call.   Please let us know, if you have any question.   Thanks, Ashish. ... View more

 Hi  vsselvaraj,   "ProgramData" folder is a hidden folder inside the " 😧 drive". Can you please check and confirm if you see the folder as per the screenshot attched (DotNetAgent_folder.png). if yes. Kindly send the folder as a private message.   If you do not find the folder in this location, Could you please verify and confirm. To deploy the WebRole ( Azure cloud service ) , did you uncheck the checkbox while installing and configuring the nuget packege on the visual studio ? Screenshot attched for your reference (  WebRole.png).   Also kindly verify and send the adInstall.log file which is located under the 😧 drive.   Please let us know, if you have any question.   Thanks Ashish. ... View more

Hi  vsselvaraj,   Thanks for the update.   Can you also provide us the latest  DotNetAgent   folder from following default location in a private message for the review ,    if this is not changed during installation default path will as below. else you can use the modified path. D:\ProgramData\AppDynamics\DotNetAgent     Answer to your question -  > No, you need not to install AppDynamics agent into you local machine.  When you install the Azure  Nuget package in Visual Studio, it is enough to deploy the cloud service in Azure cloud instance through visual studio. > No,you need not to add any Add on, to report the the cloud service mertics data at the controller UI through .Net agent,  > If i understand correclty, you have On-premise controller ? If Yes, azure agent reports the metrics details to on premise controller also.    Please send us the us DotNetAgent folder in a private message for the review. We will review the details and update you the the next course of action.   Thanks, Ashish.   ... View more

Hi Jayaram,   For to cleanly disable  .Net Agent, it will take following steps-    1) Find System Level Environment Variable by the name of "COR_ENABLE_PROFILING" and change its value to 0. 2) Stop and Disable Agent Coordinator Service ( @ Services.msc). 3) Recycle all your instrumented applications ( this step is very important because after you recycle, due to steps you took in 1) and 2), Agent Profiler and other Agent dlls will not be loaded into Process Memory and hence will stop any kind of instrumentation).   When you need to enable .Net Agent again -    1) In the System Level Environment Variable, change the value of "COR_ENABLE_PROFILING" and set its value to 1. 2) Enable and start Agent Coordinator Service ( @ Services.msc). 3) Recycle all your instrumented applications then apply the continuos load on the instrumented application.   Please let us know, if you have any question.   Thanks, Ashish. ... View more

Hi  vsselvaraj,   If we understand correctly, You have created Web Role under the  Azure Could Services after that you have installed the AppDynamics Azure Nuge packege and deployed the solution in the azure instance, but when you are browsing the application url after the deployment , you are not able to see the metric data on the controller UI   To troubleshoot the issue, could you please provide us the below details  -    1) What is the Azure agent version, which you have installed through NugetPackege ? 2) Have you applied the continuos load on the application ? 3) Please share the DotNetAgent folder from following default location, if this is not changed during installation. D:\ProgramData\AppDynamics\DotNetAgent 4) Also, please update us if it is fresh deployement or it is re-deployment over existing deployed solution ?   Thanks, Ashish. ... View more