Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > Table to identify in false alert issue

Table to identify in false alert issue

Table of contents
Created by Verwin Ubana, last modified by MindTouch on Jun 23, 2016

Views: 247 Votes: 0 Revisions: 5


Alert triggers every time you change something in the node (delete or remove node or interface).  Also, there is false alert every time the node / interface has change / delete.


All NPM versions


Tables to Identify

AlertObjects when active alert is triggered and for triggered swis entity doesn't exist record here, record is added. When alert is reset record is not deleted. About deleting orphaned record takes care database maintenance

contains currently active alerts i.e. when alert is triggered then a new record is created for a given object, when alert is reset then record is deleted for a given object.


is used just for global alerts (just one alert is triggered when more objects fulfill trigger condition). It contains a list of objects which triggered the alert.


here is stored every action done with active alert such as trigger, reset, acknowledge, added note, action execution.

AlertConditionState is used by the service to persist evaluated alert conditions
  1. Check Alerting.Service.V2.log and look ERRORS that has AlertObjectIDs.
  2. Open AlertHistory table, search for AlertObjectIDs from step 1 and take note the corresponding AlertObjectIDs.
  3. Open AlertObjects table, search for AlertObjectIDs from step 2 and take note the corresponding AlertIDs.
  4. Open AlertConfigurations an search for the AlertIDs from step 3.


Once confirmed that this is a false alert and databse is not updated, re-sync the database using configuartion wizard -- database.


Last modified