Enhanced Node Status - Alert Simplification

Hi All,

With the Enhanced Node Status that was introduced, how are users going about setting the "Severity of alert" in the Solarwinds Alert console using a single Alert rule?

I either end up with a Warning/Critical alert rule, which often triggers a duplicate Email alert, or an alert that started of as a Warning, and became critcal that shows as Warning in the Aelrt Console?

Interested in how people have tackled this situation?

Thanks!

Find more posts tagged with

Accepted answers

All comments

thiesaj

I have ~40 Alerts in my environment. We are in the process of reviewing them, but, to answer your question, part of our review process includes determining the ACTUAL severity of the Alert, versus the PERCEIVED severity.

Node/Server down? Generally a Critical Issue, EXCEPT for test servers.

Volume down to less then 15% free space available? Warning. There is a couple of us, who clean up and get them back to a manageable level.

SSL Cert Expiring in 90 days? Informational. Low ticket.

Its all about measuring what the ACTUAL severity vs the PERCEiVED severity is.

Unless you are asking for a technical implementation, then, I dont have a great answer.

vinay.by

You will need to go back to board, firstly what is it that you want to consider for your node status to turn warning on critical ? and then further drill down to specific parameters/thresholds etc then you check what's relevant for you under node child status participation and then you design your alerts accordingly

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm

Hope this helps.