Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > General information on how to debug script monitors

General information on how to debug script monitors

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

Views: 1,144 Votes: 1 Revisions: 3

Overview

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

Environment

  • All versions of SAM
  • All versions of Windows
  • All versions of Linux

Steps

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.
    a. Go to Settings > SAM Settings > Manage Applications.
    b. Select the Application that contains your script and click Edit Properties.
    c. Open the Script Monitor.
    d. Next to Script body, click Override Template.
    e. Click Edit Script.
    f. Click Get Script Output.

 

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

2. Enable debug on the Application.
    a. On the settings page for the Application, open the Advanced section.
    b. Set the Debug logging to ON. 
    c. Click Save and Continue working.
    d. Select the component and click test.
    e. 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

 

 

 

Last modified

Tags

Classifications

Public