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
Store

Alerting Question - Set Alert Severity by Custom SWQL or Custom SQL query

Wondering if it is possible to create a trigger for an alert using custom query, that will set the Alert Severity, using a custom field?

I am looking to reduce the number of alert def, if I can

The end result would be a single Node Down Alert that would set the severity off a custom field in the Node.

So if Node A is a Critical Node and the alert is triggered it would set the Alert Severity to a Higher Level, if Node B be a NON-Critical triggered a Node Down.

Find more posts tagged with

Accepted answers

All comments

adam.beedell

If by alert severity you mean the actual in-SolarWinds warning/critical/etc then I dont know a way to do it in one alert, but it would be easy to make ~5 alerts copies and bucket them to accept a custom property indicating intended priority

If by alert severity you mean what's received by the receiving ticketing system then yeah that works great and comes recommended by more than just myself

yaquaholic

Hi eem4osg

Yes, here is one way you could do it:

Create a Node Custom Property such as Critical Node True/False (Yes/No).

Navigate to your Manage Alerts view and search for the "Node is Down" alert

Copy the out of the box "Node is Down" alert and rename the copy to something like "Critical Node is Down", then add into the trigger that the Custom Property Critical Node must equal True/Yes.
Set alert severity to what ever you like, the edit the Trigger action(s) and replacing ${status} with the severity value you want.

Copy the out of the box "Node is Down" alert and rename the copy "Non-Critical Node is Down", then add into the trigger that the Custom Property Critical Node must equal False/No.
And again set alert severity to what ever you like, and again editing the Trigger action(s) and replacing ${status} with the severity value you want.

Disable the out of the box Node Down alert.

You might want to adjust the reset triggers. all depends on your scenario.

Hope it helps