APMInsight - NET Agent Onboarding - KB
Prerequisites:
- The environment should aligns with our agent's supported components( .NET Framework 3.0 Service Pack installed, Microsoft .NET runtime version 4.0 & above)
- Network and Firewall: Outbound communication from the agent installed machine to the Application Manager (Host and Port) should be allowed either directly or via a proxy server.
- The application user should have full permissions over the agent directory - C:\ProgramData\DotNetAgent & C:\ProgramData\DotNetCoreAgent
- Competitor agent of other tools like (E.g Dynatrace, AppDynamics, etc..) should be removed before installing our agent.
- SharePoint/Multi-Domain environment: Specific configuration changes required due to security concerns in these environments.
- Ensure your application
Please note that restart of your application is necessary (i.e. IISRESET cmd execution for IIS sites, restart for windows service & desktop apps) to start monitoring after agent installationAgent installation failure:
- Recheck prerequisites and try the `Installation via command line`.
- If issue still persists, locate the `apm_install.log` file in the installation directory & send the log file to appmanager-support@manageengine.com for further assistance.
App Onboarding Failure:
1. Incorrect Applications Manager(APM) Endpoint URLs configuration:
- Verify the connectivity with following cmds:
- Linux:
curl '<ApplicationsManager_Endpoint>/index.do' | grep 'Applications Manager'- Windows:
- (Invoke-WebRequest -Uri '<ApplicationsManager_Endpoint>/index.do').Content -split "`n" | Where-Object { $_ -match 'Applications Manager' }
Note: Replace <ApplicationsManager_Endpoint> with appropriate the Applications Manager server endpoint URL - If the output doesn't contains references to 'Applications Manager', the endpoint is incorrect. Update the appropriate values in Edit APM Insight .NET Agent Configuration tool.
- If a proxy server is in use, specify the proxy server configuration in the APM Insight agent's settings to ensure proper communication between the agent and the Application Manager.
2. Invalid or Empty License Key:
Possible Cause: Invalid license key will cause Monitor creation failure. Screenshot for reference
- Check whether license key entered in the APM tab's "Add Monitor" page is matches the one provided on agent side.
- If incorrect, update it and restart the agent.
Note: Any update made to the APM Insight agent's configuration requires a restart of the agent to ensure that the change take effect
3. Application not enabled:
- Ensure your application (IIS app, Windows service, desktop app) is enabled for monitoring within the "APM Insight .NET Agent Configuration" tool and your application is running & processing transactions or requests for the agent to monitor it.
- Verify if the application process(IIS app, Windows service app, Desktop app) instrumented with agent profiler using Process Explorer:
- Download and unzip Process Explorer. Run the "procexp.exe" in administrator mode
- Locate the target application process (w3wp.exe for IIS app, <service_name>.exe for services, or the main executable for desktop apps).
- In the Process Properties (Right Click -> Properties), go to the Environment tab, and Confirm the presence of the COR_PROFILER & CORECLR_PROFILER variable with the value of `989D151B-3F31-482E-926F-2E95D274BD36` & `9D363A5F-ED5F-4AAC-B456-75AFFA6AA0C8`
- Verify if the application process(IIS app, Windows service app, Desktop app) instrumented with agent profiler using Event Viewer:
- Open Event Viewer and navigate to Windows Logs > Application.
- Check for the event with the source .NET Runtime and verify that the `Process ID(decimal)` matches the one in Task Manager.
- Verify if the agent created following log files under this path - "C:\ProgramData\DotNetAgent\AgentLogs" or "C:\ProgramData\DotNetCoreAgent\AgentLogs"
- For IIS app , ".NetAgentNative.w3wp.exe.<PID>.log" , "DotNetAgentManaged.ROOT.w3wp.<PID>-<dd-mm-yyyy>.log"
- For Windows service & Desktop app, ".NetAgentNative.<service_name>.exe.17348.log" , "DotNetAgentManaged.<service_name>.exe.<service_name>.<PID>-<dd-mm-yyyy>.log"
Note: This log file will be created only if the application having or performed with some transaction
If still encounter with app onboarding failure, contact appmanager-support@manageengine.com along with these steps screenshots and updated Agent diagnostics for further assistance
New to ADSelfService Plus?
Related Articles
How to Install .NET agent on AWS Elastic Beanstalk?
One of the two options listed below can be used to install APM Insight agent onto a .NET web application hosted in Elastic Beanstalk environment via ebextensions. Deployment through AWS kit for Visual Studio. Deployment via uploading packages to AWS ...APMInsight - .NET Agent Data Collection - KB
Prerequisites: The environment should aligns with our agent's supported components( .NET Framework 3.0 Service Pack installed, Microsoft .NET runtime version 4.0 & above) Network and Firewall: Outbound communication from the agent installed machine ...Troubleshoot - Duplicate APMInsight Monitors
Introduction: Duplicate monitors might be created in APMInsight due to various reasons. This article will help you identify and resolve the issue of duplicate monitors. The common causes include: - Changes in monitor configuration. (apminsight.conf ...How to install .NET agent on Azure app services?
You can track the performance of your .NET and .NET Core web app's key metrics like response time, throughput, and Apdex score via the APM Insight .NET agent hosted in Azure App Services. Installing APM Insight extension via Azure portal 1. Log in to ...How to add an APM Insight Node.js agent in Kubernetes via InitContainers?
To integrate the APM Insight Node.js agent into your Kubernetes applications using InitContainers, follow the steps given below: Step 1: Create an empty volume that will be used to copy the agent files during the initContainers process. Example: ...