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

Best Alert Strategy?

Hello Team,
I am working with SolarWinds NPM and want to follow a professional alerting strategy.
How do you design alerts to avoid noise but still catch real issues?
CPU / Memory thresholds
Interface utilization
Packet loss & latency
Looking for advice from experienced NPM professionals.
Thanks!

Find more posts tagged with

Active

Device Details

sam

orion

npm

Status: Active

Comments

oithim_yew

For this case, you probably need a combinations of a few conditions and there is 'best' strategy. For us, our basic alert would be when the resources reaches our predefined threshold and the time. Example, if the CPU reaches 90% (our warning threshold) and lasted for XX minutes, alerts will trigger. If it is for a few seconds or minutes, we will treat it as a false alarm. I think the basic would be the if the threshold were continuous for a certain time (you will define it), it will be treated as an alert. The rest of it will be an ongoing work.