Orion Server 2020.2 application monitor template bundle

These three SAM application monitor templates were released in SAM 2020.2 to replace the deprecated Orion Server 2017.3 template.

  • The Orion Server 2020.2 - Additional Polling Engine template assesses the status of Windows services running on an Additional Polling Engine in Orion Platform 2020.2.
  • The Orion Server 2020.2 - Additional Websites template assesses the status of Windows services related to SolarWinds Orion servers running Orion Platform 2020.2.
  • The Orion Server 2020.2 - Main Polling Engine template assesses the status of Windows services on the Main Polling Engine in Orion Platform 2020.2.

Updated versions of all three templates are included in SAM 2020.2.6. Use them to monitor your Orion Platform deployment,

Prerequisites
WMI access to the target server.

Credentials
Windows Administrator on the target server.

To learn about component monitors in these templates, see:

Anonymous
  • I have 5 polling engines, all running 2020.6,  and I recently tried to apply this app monitor template to them for additional detail in monitoring.  What found is that 4 of 5 work fine.  The 5th works on the collector queues folder size sensor, but not on the others, saying "Unexpected error occurred.  Invalid query".  Everything is a perfect match between servers, including everything from user accounts to windows updates.  All have been reinstalled recently as well.  Unsure how to resolve this error... has anyone run into this before? 

  • There are 2 Process monitors within these templates - Process Monitor - SWJobEngineWorker2.exe & Process Monitor - SWJobEngineWorker2x64.  They give you the number of running copies, but you cannot alert on the number of running copies, Plus setting the thresholds is strange on these as the total %CPU and  % Memory thresholds go over 100% as these seem to be based on sum of % used - is this the case?  Should we be setting this over 100% as it seems to be counter intuitive.  Please can someone give me some pointers on setting these thresholds?

  •   Thank you for info.  Yes this helps and makes sense how you described it.  

  •  I checked with the person that created these templates and here's the response:

    • Many of those component monitors are performance counters that only some customers need, depending on environment and scale, so they're disabled, by default. 
    • They're included so an escalation engineer can enable them to troubleshoot any issues with polling, the SolarWinds Job Engine, or SolarWinds Collector services.
    • You can enable them but they may cause unnecessary noise until thresholds are set correctly for your particular environment.

    Hope this helps!

  • Sorry for the silly question.  I notice many components are disabled after I downloaded these.   Is the idea that these components are really used my most for Orion monitoring?  I think there maybe some that may be applicable so they can be enabled in my environment,  Just curious why disabled from start.  After moving to 2020.2 my old monitors don't seem valid much anymore so these new template is great!