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

Escalation Level at 0 despite alert being triggering

Hi,

We have a Solarwinds instance monitoring our systems. In the past few days, we seem to have somehow got to a position where the escalation level on an active alert is remaining at 0, even though the alert has triggered. This means the actions of the alert are not triggered. We have an alert set up to be intentionally triggered twice a day just to alert our teams that certain systems are still working. This alert appears to be working correctly with the escalation level going to 1 in the morning, but in the evening the escalation level remains at 0.

It seems that perhaps something has been set somewhere to lower escalation levels at certain time(s) of the day, or something similar. I can't find anything related in the settings, though.

Any suggestions would be greatly appreciated!

Thanks.

Find more posts tagged with

escalation level 0

Accepted answers

All comments

monitoringlife

Whats your escalation chain logic? Are any timers involved? If not have you had any reboots of the SQL server (and/or cluster failover)?

PC123

Thanks for responding.

There aren't any timers set - it should go to level 1 as soon as the alert triggers. We don't have a level 2, etc set.

SQL server hasn't been rebooted recently, though our Solarwinds servers have. I've now bounced the SQL box as well, just in case.