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

Condition must exist option doesn't seem to be working correctly since upgrading to SAM 2020.2.x

I have a couple custom alerts setup that polls nodes being down. I don't want to catch a reboot so I set the 'Condition must exist' option to 30 minutes. This has worked fine until we upgraded SAM to 2020.2.x. Now this alert fires on reboots which we get a ton of alerts every night because of scheduled server reboots. Has anyone else seen this issue since upgrading?

Thanks

Greg

Find more posts tagged with

Accepted answers

All comments

bogdan.stan

Works fine for me on 2020.2 first release.

tony.johnson

Unable to reproduce in my 2020.2.1 lab. Can you post a screenshot of the Trigger Condition?