Troubleshooting Inconsistent .NET Core monitors Availability
Issue: Some applications are experiencing inconsistent availability status, where they appear to be active but are reported as "down." This issue can occur due to the nature of application monitoring and how the monitoring agent interacts with the application pool's idle time settings.
Follow below troubleshooting steps to address inconsistent availability issues for monitored applications:
1. Log in to the IIS server console where the applications are hosted.
2. For the application pool associated with the monitored application, configure the "Idle Time out Action" as "Suspend" instead of "Terminate"
Reason: When the "Idle Time out Action" is set to "Terminate" the monitoring agent may terminate the Worker process (e.g., dotnet.exe) during periods of inactivity. This termination can lead to the application being reported as "Down". By setting the configuration to "Suspend", you ensure that the Worker process remains active, and the monitoring agent can continue communication even during idle periods. Communication will only stop when the IIS site or application pool is manually stopped.3. Monitor the application's availability status. It should now accurately reflect the application's state, turning green when transactions occur and accurately showing "Down" when the IIS site or application pool is stopped.
New to ADSelfService Plus?
Related Articles
While trying to monitor servers, I get a "No data Available" error for CPU Core Utilization.
The data for CPU Core utilization may not be shown due to problem in executing and getting the output of CPU command on the server. For different modes of monitoring (WMI/Telnet/SSH/SNMP) we use different methods to collect data. Find the steps below ...How to change .NET Core application's name?
1. Navigate to the application published directory. 2. Create or open the apmapplication.conf file, then add or modify the application name. application.name="[YourApplicationName]" Note: Changing the application name only creates a new APM Insight ...How to generate the .NET Core agent diagnostics zip file?
To learn how to generate the .NET Core agent diagnostics zip file, click here.Folder path to view the .NET Core agent logs
The logs of the .NET Core agent can be found at the destination that was configured during the agent installation. E.g ./InstallAgent.ps1 -Destination "G:\.NET_Core_Agent" -InstallType "local" -LicenseKey ...To monitor Self Contained .NET Core applications using .NET Core Agent Loader API
By default, when you install an APM Insight .NET Core agent, the agent will be loaded along with the .NET dependencies configurations. But in the case of self-contained applications, this is not possible. In these cases, you can install the .NET Core ...