PowerShell monitor for Office Web Apps server

To start, you have the output parts backwards, it should be Message.Health and Statistic.Health.  Or, if it's just the one part, you can ditch the .Health on the end, SolarWinds is happy with either.  This is likely the reason you're getting the "Not Defined".

The second issue you have is that you are not doing anything if the status is not healthy, unless you're just giving a test script.  You should have a condition for health, and unhealthy.  I'd probably do something like this:

Import-Module OfficeWebApps
$health = (Get-OfficeWebAppsMachine).HealthStatus
if ($health -eq 'Healthy'){
    $stat = 0
} else {
  $stat = 1
}


Write-Host "Message.Health: $health"
Write-Host "Statistic.Health: $stat"
Exit($stat)

Something to consider as well, I'm not sure if it's the case for PowerShell scripts, but the exit code of the script also impacts the reflected status.  Various status codes are written up in the admin manual, there are codes for VBscript, Nagios, Perl, etc, but not seeing one listed for PowerShell.  If they do still apply, 1 is "WARNING".  You can also adjust that by setting the warning/critical thresholds for the component.

Hmm. I tried that script; set for Remote execution.

Get Script Output returned 'Not Defined' for the Output Result.

I can run the script via a remote session with the same credential.

I'm assuming the script monitor doesn't require a looser execution policy than RemoteSigned?

They my not have mentioned it because there's the whole separate document on using SAM with PowerShell.

if you're running the script in Remote mode, you'll want to test it via a local session on the target system, not a remote session on your system. Does that make sense? Log into the target system and try to run the script locally. Your script is at the mercy of the target system's configuration.

Yep; I tried running it that way and it seemed to run fine. No errors and it returned data.

Can you show us the latest revision of your code?

Can you provide a screen shot of the configuration,and the test results when you click the test button?

Here's the current script:

Import-Module OfficeWebApps 

$health = (Get-OfficeWebAppsMachine).HealthStatus 

if ($health -eq 'Healthy'){ 

    $stat = 0 

}

else { 

  $stat = 1 

} 

Write-Host "Message.Health: $health" 

Write-Host "Statistic.Health: $stat"

Exit($stat)

Monitor setup:    http://dsolodow.github.io/SAM_PowerShell_script_setup.PNG‌

Test results:    http://dsolodow.github.io/SAM_PowerShell_script_results.PNG

What happens when you try to run this same script in a 32bit PowerShell session?

My guess is the cmdlet fails to load. If that's the problem then you need to change the Platform to run the polling job on within the application from x86 to x64, as shown below.

So it turns out the script was fine. The reason it was failing out was due to a wsman remoting issue. Derp.

Amazing how much better remote scripts run when that's working.

One follow-up question though; where's the list of exit code to status mappings?

What I want it to do is be if status = a, show as up, if status = b show as down, anything else show as unknown.