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

Question on Node states

Hello,

My company has been using Solarwinds to monitor radios out in an oilfield. We have email alerts that go out when nodes go down and I have been building dependencies to reduce "alert storms"

However, the dependencies only stop child alerts if the parent goes down, but not if it goes into a critical state, which I am alarming on as well. Is there any way to change this? what is the difference between down and critical?

Find more posts tagged with

Accepted answers

All comments

mesverrum

The whole dependency scheme only takes into account up and down statuses, so it has no impact on any alert types that involve something going wrong but not taking the node down.

At the simplest explanation a down node is something we can't ping anymore, it can go critical for a ton of reasons such as having problems with a child object like an interface/application or exceeding a resource threshold. As long as its still pingable it won't show as down though.

ioan_bucsa

If I understand correctly you are alerting on node statuses including 'Critical'. Like @mesverrum pointed out, node status is affected by the statuses of all its child objects.

My recommendation is that you fine-tune the alerts and trigger on hardware sensors, interface utilization or resource utilization (CPU, memory, disk etc) changing status to 'Critical' instead since: a) the alert becomes more meaningful; b) you speed up the troubleshooting process by narrowing down the root cause.