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

Creating an alert for "other conditions"?

We have a fairly small environment, about 200 servers, that are being monitored. The server team has asked me to fine tune the Warning and Critical alerts so that the alerts are reporting on individual characteristics having issues, such as high CPU, memory and disk usage. I've created alerts for CPU and memory, but I'm trying to wrap my brain around how to create an alert that excludes CPU and memory from the conditions.

Find more posts tagged with

Accepted answers

All comments

KMSigma.SWI

I'm trying to wrap my head around the logic of it. Do they want "alerts" for when CPU is over Warning and a different for when it's over critical? Do they want the same for memory? How about disk IOPS or space?

Because right now that reads as between 8 alerts you'd need to craft - just there.

CPU > Warning
CPU > Critical
Mem > Warning
Mem > Critical
IOPS > Warning
IOPS > Critical
Space < Warning
Space < Critical

I think you might need to consider having a better talk with them about what they are hoping to accomplish with these alerts. If I had one system acting wonky, then I could get 4+4 emails (as they moved from warning to critical thresholds) per system. This seems like a very bad plan and a sure way to have people suffer from alert fatigue.

CHoogerhuis

Ok, we were suffering from Alert Fatigue (TM), because we got alerts when our database servers hit 100% CPU, disk or memory usage. I have since grouped them in their own groups, and we get a morning report on what's been going on with them rather than an e-mail each time someone runs a SQL report.

To them, warning and critical alerts are the same, so one works just fine. But they'd like to get e-mails when it is NOT a CPU, memory or disk issue. So a way to weed out those three criteria for the alert.

KMSigma.SWI

What are the other alerts we are talking about here? The stuff from AppInsight for SQL or something else that I'm missing?

CHoogerhuis

KMSigma.SWI

You are my favorite person this Monday for putting up a Mal Reynolds GIF. #Browncoats