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 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 installationCase1: Monitors shows "UP" but No data collection
1. No App traffic
- The monitored application doesn't have any transactions in the selected time window. In such cases, make some transactions/traffic and check after some time.
2. Application Changes
- If the respective application has replaced/renamed/moved in the IIS server, a new monitor instance might have been added and the old monitor would have no data to report. In such cases, kindly suspend (if historical data is required) or delete the monitor.
- Since the applications are mapped to their respective IIS paths, any change to the physical path of the application will require an update to the App Filters.
Case2: Monitors shows "DOWN" & No data collection
1. Could not Connect to Host (Applications Manager Endpoint):
- 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 License Key:
Possible Cause: Invalid license key will cause app monitoring 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. Unmanaged/Suspended state
Monitor might unmanaged/suspended from the Applications Manager UI.
Action: So,Verify if the app monitoring status appears in the Health monitor tool as "Suspended" state. If yes, Activate or Manage the app monitor from Applications Manager UI.
4. License Expired state
Monitors addon license might got expired or addon licensed not enabled on the Applications Manager.
Action: So, Verify if the app monitoring status appears in the Health monitor tool as "LicenseExpired" state. If yes, ensure the `APM Insight .NET AddOn` licensing enabled to allow .NET app monitoring on the Applications Manager.
5. Monitor Licensing Count Exceeded state
Monitors licensing count might exceeded on the Applications Manager.
Action: So, Verify if the app monitoring status appears in the Health monitor tool as "LicenseExceeded" state. If yes, ensure the extra monitor licensing enabled to allow .NET app monitoring on the Applications Manager by unmanaging the existing one or apply extra monitor count license.
6. Application Crash
With agent installation, application might get crashed due to Sharepoint/Multi-domain apps or Unsupport DLLs methods or agent with app DLLs conflicts
Actions:
If still encounter with app onboarding failure, contact appmanager-support@manageengine.com along with 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 ...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 ...APM Insight monitor is UP, but monitor page doesn't show any data
Possible Causes The APM Insight monitor status corresponds to the respective agent folder pointed Java Application status i.e., as long as the Application server is running, the monitor status will be UP. 1. No Transactions Recorded: It is possible ...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 ...How .NET agent collects data?
APM Insight .NET Agent is a profiling based monitoring solution. It uses the profiling APIs provided by Microsoft frameworks and hooks itself into the ASP.NET worker process. The general workflow for monitoring is as given below : The .NET agent ...