Powershell script monitoring (SAM 5.2)

I have created a Powershell script to monitor multiple Windows Services. The script runs perfectly from a PS promt, returns the correct exit code, statistic and message. When I test the script in SolarWinds, I get the following:

Output when testing with the services all running-

Message.Status:All services are running
Statistic.Status:0

Values in the SolarWinds APM_ComponentAlertVariable table.

ComponentID MultiValueStatistics MultiValueMessages
4151 Status:0.00 Status:All services are running

Output when testing with a service stopped-

Testing on node 'XXX.XXX.XXX.XXX' failed with 'Down' status ('Down' might be different if script exits with a different exit code).

Output: ==============================================

Statistic.Status: 1

Message.Status: Apache Tomcat 9999 (Stopped)

Values in the SolarWinds APM_ComponentAlertVariable table.

ComponentID MultiValueStatistics MultiValueMessages

4151 Status:N/A Status:N/A

These values do not change as long as the service is stopped. When I restart the service, The values are updated as shown above in the "Services all running section".

Statistic.Status is the number of services down.

Message.Status is the display names of the services down.

My alert is using the ${MultiValueStatistics} and ${MultiValueMessages} variables so I get an alert stating "# of services down : N/A, Service Names: N/A".

I have atteched the script I am using in the monitor. Any guidance or help would be greatly appreciated.

ps_test.ps1

Find more posts tagged with

apm_monitoring_template

application_monitor

PowerShell

Accepted answers

lukas.belza

Hello,

The problem is with the exit code. If the script ends with exit code 1 (Down status) then the outputs of the script are ignored (and all statistics and messages are set to N/A). For your case please try to use $exitcode=2 (Warning) or $exitcode=3 (Critical). For Up, Warning, Critical statuses the output of the script is correctly parsed and you should see the expected values using the ${MultiValueStatistics} and ${MultiValueMessages} variables.

I hope that helps.

Thanks,

Lukas Belza (SolarWinds development)

All comments

lukas.belza

Hello,

I hope that helps.

Thanks,

Lukas Belza (SolarWinds development)

rlibby

Lukas,

Thank you. That works perfectly. I knew that I was missing something.

Robert

muckman

Fast forward 6 years and this behavior is still present in the current version of SAM 6.9. I really don't agree that exit code 1 should behave this way.

SAM oputputs the following upon exit 1
"The return code is different than expected. Testing on node '#.#.#.#' failed with 'Down' status ('Down' might be different if script exits with a different exit code)."

When really the return code is exactly what I defined.

Can we not spew this erroneous error message? I would expect that error if the script completely failed to run not if it hit a specific exit code with a specific output.