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

Temporarily Disable Advanced/Syslog Alerting

Does anyone have any experience with how to temporarily disable alerting from within the Orion package during a maintenance window?

I am familiar with the checkbox for Basic alerting to disable pageouts which used to work great, but I am primarily using Advanced Alerting which does not have that option. I have also written quite a few rules for both the syslog and trap manager, which I would also like to suppress during change windows so as not to wake up the on-call person.

I am also running the Hot Standby Engine, which might complicate matters somewhat.

Does the "Solarwinds Alerting Service" pertain to the advanced alerting only? I had disabled this service but still received pages from the basic alerting engine, which I found interesting. I did not check the basic box to disable, as I only use a few packet loss features there. I can confirm the alerting engine was stopped on both primary and secondary polling servers.

Maybe the easiest way to kill all the alerts is to disable the mailbox associated with the on-call delivery

Find more posts tagged with

alerting_engine

advance_alerts

Accepted answers

bleearg13

In 9.5, the Advanced Alert engine has an option to temporarily disable all alerts. Is this what you're looking for?

As for Syslog Server, I've created a rule at the very top of my configured rules that disables actions on all rules for all messages. During maintenance, I check this rule and disable it when done.

alert_disable.png

All comments

FormerMember

Does the "Solarwinds Alerting Service" pertain to the advanced alerting only?

Correct.

Generally, during a maintenance window, users unmanage the devices, so no new data comes in to trigger any alerts.

euphorik

That works great when I'm doing maintenance on a single device, but if I need to reload a core device, I end up triggering alerts for dependant devices.

I tend to shy away from writing dependancies, as hiding devices that are down sometimes masks the severity of the problem. (ie. getting pages for one device down, vs. 60 pages for a bunch of other stuff also down.

I guess I'll have to shut down the trap/syslog/alerting services during any major maintenance windows.

janaka17

hi,

if i disable "solarwinds alerting engine" service,will it disable all alertings?

Thanks,

Janaka

bshopp

It will only disable Advanced Alerts I beleive, not Basic. What problem are you trying to solve by disabling that service?