Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion environment Health Checks

Orion environment Health Checks

Updated November 22nd, 2016

Overview

This article will show you how to perform Health Checks to confirm that your Orion environment is functioning correctly. 

Environment

​All NPM versions

Detail

Before performing any of the Health Check tests, consult the Orion Minimum Requirements documentation.

 

Also see the article Troubleshoot Orion Platform deployment health.

Active Diagnostics

Active Diagnostics is a self-help tool created for Health Check tests.

  1. Launch Active Diagnostics:
    • Use the Start menu search in Windows and search for Active Diagnostics.
    • You can also launch Active Diagnostics from the Orion Diagnostics application available on the Start menu: Open Active Diagnostics from the Start Menu, and click the SolarWinds Active Diagnostics link at the bottom of the window. 
  2. On the SolarWinds Active Diagnostics screen, click the Scan for know defects button.

 

The Scan for known and potential issues (default) option produces an easy-to-read report showing only or Failed (Known issues) or Warning (Possible issues) tests.

 

To run tests individually, select Run individual tests, and click Run tests for tests you are interested in.

 

The test results based on the test definition display on the right. The definitions are updated in the Active Diagnostics Self-Test.

 

To share the results of tests with the SolarWinds support, click Export results. This exports the tests results in a JSON file format. 

 

Other Performance Counters

These are Performance Counters that can be loaded on monitored from the SolarWinds Orion servers.

System Counters

Counter

GOOD

WARNING

CRITICAL

note

\Processor\%Processor Time <60 >60 >80  
         
\Memory\Committed Bytes       Depends on installed modules
\Memory\Available MBytes >2000 <1000 <100  
         
\LogicalDisk(*)\Avg. Disk Queue Length <2 >2 >10  
\LogicalDisk(*)\Current Disk Queue Length  <10  >10 >32  
\LogicalDisk(*)\Avg. Disk sec/Read  <0.012 >0.012 >0.020  
\LogicalDisk(*)\Avg. Disk sec/Write <0.012 >0.012 >0.020  
\LogicalDisk(*)\% Idle Time <80  <50 <10  
         
\Network Interface(*)\% Network Utilization <50 >50 >80

% Network Utilization doesn't exist as a normal performance counter,

Multiply \Network Interface(*)\Bytes Total/sec by 8 (to convert it to bits total/sec),

divide by \Network Interface(*)\Current Bandwidth, and multiply the result by 100 to get %.

 

Other useful system counters used for performance optimizations

Counter

GOOD

WARNING

CRITICAL

note

\System\Context Switches/sec < 35000 >35000 >45000  
\System\Processor Queue Length <=12 >12 >20 Microsoft counter documentation: the expected range of processor queue length on a system with high CPU activity is 4 to 12
\System\System Calls/sec < 300000 >300000 >500000  
\System\Threads < 3500 >3500 >=5000  

IIS Counters

Counter

GOOD

WARNING

CRITICAL

note

WebService\Current Connections       Threshold: No specific value. To be defined based on baseline measurement.
WebService\Current NonAnonymous Users       Threshold: No specific value. To be defined based onbaseline measurement.
ASP.NET Applications\Sessions Active       Threshold: No specific value. To be defined based onbaseline measurement.
         
WebService\Bytes Total/sec       Threshold: No specific value. To be defined based onbaseline measurement.
ASP.NET Applications\Requests/Sec       Threshold: No specific value. To be defined based onbaseline measurement.
ASP.NET Applications\Requests Executing       Threshold: No specific value. To be defined based onbaseline measurement.
ASP.NET Applications\Request in Application Queue       Threshold: No specific value. To be defined based onbaseline measurement.
         
ASP.NET Applications\Request Execution Time < 1000   > 10000 The number of milliseconds that it took to execute the most recent request.
         
ASP.NET Applications\Requests Total N/A N/A N/A Threshold: No specific value. Depends on load and test duration.
ASP.NET Applications\%Requests Succeeded > 99,5%   < 98%

It doesn't exist as a normal performance counter. 
Calculate it as ASP.NET Applications\Requests Succeeded divided by 
ASP.NET Applications\Requests Total 

ASP.NET Applications\%Requests Rejected < 0,5%   > 2% It doesn't exist as a normal performance counter. 
Calculate it as ASP.NET Applications\Requests Rejected divided by 
ASP.NET Applications\Requests Total 
ASP.NET Applications\%Requests Failed < 0,5%   > 2% It doesn't exist as a normal performance counter. 
Calculate it as ASP.NET Applications\Requests Faileddivided by 
ASP.NET Applications\Requests Total 
ASP.NET Applications\%Requests Timed Out < 0,5%   > 2% It doesn't exist as a normal performance counter. 
Calculate it as ASP.NET Applications\Requests Timed Out divided by 
ASP.NET Applications\Requests Total 

 

 

Last modified

Tags

Classifications

Public