Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > ipMonitor > Convert ipMonitor scripts to Orion APM

Convert ipMonitor scripts to Orion APM

Table of contents
No headers

Any script used in ipMonitor is not directly compatible with APM, since APM is more powerful and flexible. ipMonitor scripts would need to be modified for use with APM, as described below.

With ipMonitor scripts:

  • Third party monitor expects a specific exit code to be returned by an exit code or environment variable.
  • You indicate what the expected value should be, and pass/fail is based on that value.

With APM scripts:

  • The script returns 0 (for up), 1 (for down), 2 (for warning), or 3 (for critical).
  • APM can track a statistic as returned by the script. Send the following through standard out: “Statistic: #<CRLF>” to allow APM to track the value over time. This is a required field (if no statistic, return 0).
  • APM can include a textual message to send back to the UI or alerts. Send the following through standard out: “Message: Your message goes here<CRLF>” to allow APM to track an error or information message. This is not a required field.


For more details (on how we also do Linux/Unix scripting) see the section “Creating a Linux/Unix Script Monitor” in the SolarWinds Orion APM Administrator Guide.

Last modified
15:22, 13 Nov 2015