Applications Systems

General information on how to debug script monitors

This article provides some information on troubleshooting issues with SAM's script monitors.

First published date

10/17/2018 2:37 PM

Last published date

10/17/2018 2:37 PM

Overview

This article provides some tips on troubleshooting issues with SAM's script monitors.

Product section

Server Application Monitor

Resolution

Generally there are two ways to help you isolate an issue with running a script via a Script Monitor (Windows Script Monitor, Windows Powershell Monitor or Linux/Unix Script Monitor):

 

  1. Use the Get Script Output feature.
    1. Go to Settings > SAM Settings > Manage Applications.
    2. Select the Application that contains your script and click Edit Properties.
    3. Open the Script Monitor.
    4. Next to Script body, click Override Template.
    5. Click Edit Script.
    6. Click Get Script Output.

This should provide the error being returned by the script or if the monitor is misconfigured.
 

  1. Enable debug on the Application.
    1. On the settings page for the Application, open the Advanced section.
    2. Set the Debug logging to ON. 
    3. Click Save and Continue working.
    4. Select the component and click test.
    5. Open the Application Debug log file in the following directory:

      C:\ProgramData\Solarwinds\Logs\APM\ApplicationLogs\AppId[##]\

Note: ## is the internal ID of the Application, as seen in the Browser's address bar when viewing the Application's settings.
This log should provide information on the script run and the response received