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

Trigger alert when threshold is warning/critical

Hi I am running SAM v2020.2.4 and have created a monitor template which script output sets the Print:Statistic to 2 for warning and 3 for critical, for each statistic there is also a Print:Message ( prints failed devices)

I am looking to get an alert based on this output: If the threshold is at warning or critical, trigger alert and add the Print: Message output to alert.

I have created above alert, Am I on the right track ?? and how would I add the Print:Message to it ??

Is there a way to trigger alert on threshold status other than constantly polling it to check status ???

Thanks

Find more posts tagged with

Accepted answers

All comments

Seashore

No, I think you should on the actual SAM component set "Warning if statistic=2" and "Critical if statistic=3".

Then on the alert rule you can say "alert when component status is warning/critical".

I always try to just have one (or at least very few) alert rules. Having a single alert rule that triggers if an application is critical, nomatter what you monitor, is enough most of the time.

I think this is the variable that shows the component message: ${N=SwisEntity;M=ComponentAlert.ComponentMessage}

mesverrum

Another trick you can do is manipulate the exit codes inside your script, https://documentation.solarwinds.com/en/Success_Center/SAM/Content/SAM-Script-Report-Status-Through-Exit-Codes.htm

Exit 1 is a down, 2 is warning, 3 is crit

Seashore

Hmmm, interesting. I haven't tried that one. Not sure how I will use it in reality but it's always good with more tools. Got to test that, thanks!

fraser-sky

Thank you all for your suggestions

I did look at Exit codes but couldnt get my python script to work with them but managed to use the Statistic to set the level of the monitor which worked.

But I have changed things a bit now so only a Statistic=3 will change status of Monitor to warning.

So I have an alert that triggers on - Component Alerting Properties - Multi Value Statistics - is not empty

which emails report and displays the Messages for all Component values whether the Statistic is 1, 2 or 3 ( ${N=SwisEntity;M=ComponentAlert.MultiValueMessages}) - this shows messages for all components

Thanks Seashore - you put me on the right message track.

I have a second alert that triggers when the application is in a warning state which generates a ticket as Statistic=3 indicates an issue.

That is how I got it working on our system but seems there are many different ways to go about it.

Thanks again