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

Alert on Alert Status

This feels like a stupid question but here we go!

Let's say I want a trigger condition based on an alert status of another alert... I know I can SWQL finding active / triggered alerts but Trigger Conditions don't seem to have that scope available to them?

Find more posts tagged with

Accepted answers

KMSigma.SWI

They do not - and this is intentional. There's a chance that you could build an "endless" query. It's a limitation and if you feel you need something like this, then you should put in a Feature Request.

All comments

KMSigma.SWI

gregthompson

Now I'm sad.

KMSigma.SWI

How about you give us the scenario and we can put our heads together and see if we can't come up with an alternate solution.

gregthompson

What I wrote here basically... https://thwack.solarwinds.com/product-forums/the-orion-platform/f/alert-lab/97535/single-instance-of-an-alert

Because potentially thousands of interface sensors are created as nodes are added I wanted to use an Alert that looked for ANY that met our criteria to be disabled since we need some enabled/some disabled. To have this Alert fire 1 time regardless of how many it found then wait X minutes before it allows a re-trigger.

Since the powershell script we're running contains the same trigger conditions it's going to find ALL the sensors that met the same criteria and in 1 fell swoop they all get disabled.

This is more efficient then overlapping powershell scripts as each node is evaluated for it's child sensors.

I could have it pass the parent node to the script and help limit the amount of powershell's that are executed but if we do a bulk add it's still going to run a lot of Alerts/scripts.

Think of it like a flapping detection on a device with a simple check "if you ran in the last X minutes, don't trigger".