Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SWIS PowerShell Add application monitor to Node

I have a script that adds a node and populate all the custom properties used in our environment. I'd like to apply an application monitor to the node automatically if a specific custom property matches a specific value. I looked around and wasn't able to find anything in the discussions.

Is there a way to add a monitor to a node via Swis PowerShell?

Find more posts tagged with

Accepted answers

All comments

kenyamson

@isaacs you may refer to OrionSDK/Samples/PowerShell/SAM.Application.ps1 at master · solarwinds/OrionSDK · GitHub. You'll need to create a query on the node based on the custom property you have and then use the assign template function.

SteveK

Hi @isaacs,

This functionality already exists within SolarWinds itself.

First you would need to create a group (All Settings -> Manage Groups -> Add New Group). Then you would create a group with a Dynamic Query. The dynamic query would be whatever your custom property and value are.

Then under Sam (Settings -> All Settings -> SAM Settings -> Manage Templates), then click the button to assign to group and complete that wizard.

As @kenyamson mentioned there are was to do it via Swis, but I always try to go with the solution baked into the product before going custom. The link they mentioned lines up withs stuff I used in the past. If you need to set custom properties to the SAM monitor, then I would probably go the script approach, or have a script scanning for that monitor without properties and have it set it after the fact.

isaacs

Thanks everyone! I was able to get it working as expected.

SteveK

Which route did you end up going?

isaacs

I went the SWIS route since in my case, while the add node script I created was running, I needed to add specific application monitors based on custom property values and other variables. For example, if a third-party service is installed and found during the script execution it will add the related application monitor\alerts automatically reducing the possibility of critical service monitors not being added.