Migrating IPMonitor External Processes to Orion SAM

antcooper

Currently in IPmonitor we have External Process monitors that run a cmd and return a value that we use to then setup alerts for. What would be the best method of setting up the same monitor in Solarwinds SAM? Would a powershell script that runs the CMD be the best solution or are there other alternatives? If powershell is the best solution are any examples available that could be built off of?

Below is an example of one of our setups in IPmonitor

weston.hood

Yes, I would have SAM do it via Powershell. If you have access to that cmd (C:\Program Files (x86)\VertexMonitor\testvertex.cmd) then I would copy and paste that script into chatgpt and ask it to rewrite the cmd to work in powershell (trust me, it will get you 99% of the way there, maybe all the way). You may need to then format the PS script so that it's compatible in SAM - sam wants output pairs which are comprised of 1 mandatory integer return and 1 optional string result (you can have up to 10 total pairs). Basically, it just needs this:

Write-Host Statistic: $result
Write-Host Message: "optional text output $result"

If you want more examples of the formatting of PowerShell scripts in SAM, you can go to the Manage Templates page [https:// YourHost /Orion/APM/Admin/ApplicationTemplates.aspx], and the upper right has "Manage Component Monitors within templates," click it.

 

Here you can group by Component Type and select Windows PowerShell at the bottom. There are probably around 300+ PS script components you can check out the formatting and syntax. You may notice excessive use of exit codes in the scripts, these are completely optional. And I would actually recommend almost never using them since it's easier to use SAMs built-in thresholds.