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

Alerts failing to fire

Selspiero

Hi there,

Have NPM and SAM set up and alerts have been working fine. Upgraded to the latest version last week, and have noticed that our normal alerts that are set in advanced alert manager are not firing. Example being a simple reboot alert - this should email a couple of people and write to the log (and displayed on the web site)

I'm not sure where to start with troubleshooting this one, all of the alerts are as they were last week, all solar winds services are started on the server...

any pointers to log or anything would be great

Thanks

Find more posts tagged with

Accepted answers

netlogix

Another thing I have seen that causes alerts not to fire is by using the alert suppression tab. The use case for that tab is confusing and should be avoided unless you *have* to use it. You don't have anything in that tab, right?

(Just change the trigger condition tab to not include what in the suppression tab)

All comments

shuth

There is a checkbox within the Alert Manager that disables all alert actions. Open up Alert Manager and view the Active Alerts (the blue triangle or View - Active Alerts). In the top right there is a checkbox to disable all actions. Verify this is unchecked.

You can also check the Windows Event Viewer. Under Applications and Services Logs there is a SolarWinds.Net section. Alerting Engine errors should be listed in here.

Selspiero

thanks for the reply mate.

Alerts are enabled, as if i create a new alert from scratch it works.

The only thing in the log that might point to a problem is this:

2012-08-21 02:06:49,936 [AlertCheckingThread] WARN Error - Error in UpdateRowsThatAreTriggered() - GetNetObjects

System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()

at System.Data.SqlClient.SqlDataReader.get_MetaData()

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)

at AlertingEngine.CheckAlert.UpdateRowsThatAreTriggered()

but it does not co-incide with the alert firing

thanks again for the help

mharvey

If you are seeing a large number of timeouts, then I'd recommend a quick stop of the services, then find the SWNetPerfMon.db file on the NPM install directory. Edit this file in notepad and change the timeouts at the bottom of the file from the defaults of 20 and 90, to 600. Save the file, then restart the services. To see if the alert is firing and not just firing the actions, you can check the AlertLog table in the database. First, find the alert in the Alertdefinitions table and make note of the AlertDefID. Find this value in the AlertLog table and see if there was an issue with just the actions. If this cannot be found in the AlertLog table, then in the AlertDefinitions table you can check the error columns to see if there was an issue with the alert trying to fire.

Regards,

Matthew Harvey

Loop 1 Systems

http://www.loop1systems.com

netlogix

(Just change the trigger condition tab to not include what in the suppression tab)