nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Advanced Alert: Trigger & Reset Actions

mdriskell

I have a question regarding alert actions.

I have an advanced alert that is set to send an email when a node goes down. The action is only taken if the node is down for 3 1/2 minutes to prevent the action being taken on bounces.

On the same alert I have a reset action set to send an email after the node has been back up for 10 minutes.

What I am seeing is that I am getting the reset actions even though the device never met the minimum trigger actions. From what I can tell in the configuration there is no setting to say only execute the reset if the trigger took place.

I have already applied the appropriate hotfix hoping that would take care of the issue. Am I understanding the syntax right will my reset happen regardless of the trigger?

Any help would be appreciated.

Find more posts tagged with

Accepted answers

All comments

mark_wiggans

mdriskell-

just curious as to how exactly you have the alert set-up?

Suppress Alert when all of the follwing apply-

Trigger Actions: Send new Syslog Message to ????

Log Alert to xxxx.txt???

mdriskell

No suppress actions configured. I have also noticed that sometimes I only get the Reset actions on alerts that should have been triggered.

Action taken is to send an email

Trigger Conditon

Node Status is not equal to UP

Vendor is equal to Cisco

mark_wiggans

I just sent you a PM-

lavelanet

I have the exact same problem. It's not just you.

jalvarez

This is a known bug that Solarwinds is working on. They say it will be addressed in the next release, and that the Advance Alert Engine will be totally re-written.

Regards

mdriskell

Thanks for everyone's thoughts. After opening a ticket with SW it appears that my issue has been resolved.

I know this thread has been dead but there is nothing I hate worse than trying to find an answer and reading thread after thread and never seeing a resolution.