Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Script monitor does not provide statistic value if the script exit code is 1

Script monitor does not provide statistic value if the script exit code is 1

Created by Chris Foley, last modified by MindTouch on Jun 23, 2016

Views: 1,970 Votes: 0 Revisions: 3


The following script monitors do not provide the statistic or message output value if the script exists using the exit code 1:

  • Windows Powershell Monitor
  • Windows Script Monitor
  • Linux/Unix Script Monitor


  • All SAM versions
  • All Windows versions


An exit code of 1 inicates that the script has failed. As such, no parsing of output is performed to gather Statistic or Message values.


To monitor a value and compare it against a threshold, set the statistic value as needed and exit with a value of 0. You can then adjust the thresholds within the Monitor to fail or not, depending on the value received.


Last modified