Using SAM 5.2, our organization is monitoring each separate app pool on each separate Windows Server. But every time the app pool recycles, it can take anywhere from 5 minutes to 25 minutes for the app pool to rebuild. SolarWinds triggers an alert that the application is down, when it is in fact just recycling.
More info:
What was done is we created on app template called "IIS App Pool -- APP1". We added one component to the template, which is the "Process Monitor - WMI". The process name is "w3wp.exe" and the app pool name, "APP1" is in the command line filter box. This template has been duplicated for each app pool that we want to monitor. As an example we have more templates for APP2, APP3, and so on...
This works very well for being able to capture metrics for each individual application pool in IIS and we are polling the app pools every 60 seconds. However, every time the app pool recycles SolarWinds triggers an alert that the application is down. We changed the polling to 120 seconds, 5 minutes, 10 minutes, and so forth but the alerts still occur when the app pool is in the middle of recycling.
Are there any recommendations on how to handle this situation? We want to keep our metrics and we WANT SolarWinds to alert us when there truly is a problem with an individual app pool on a server (such as if the app pool is frozen or eating up CPU or RAM). But I just don't know how to move forward. Any ideas?
** At this moment in time our organization is using SAM 5.2 --> We are waiting to upgrade to 6.0 when it goes gold.
Any ideas?