Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Alerts trigger again after the service\server is restarted

Alerts trigger again after the service\server is restarted

Created by Matthew Lamb, last modified by MindTouch on Jun 23, 2016

Views: 1,326 Votes: 3 Revisions: 3

Overview

All active alerts that are over 30 days old trigger again and fire out the action assigned to the alert whenever the alerting services or the server itself is restarted.

Environment

NPM 11.5.2 and 11.5.3

Cause 

This issue is caused by a bug within Core itself. Once the active alerts move past 30 days, the history for the alerts are cleared from the alert history tables. When the service restarts, it attempts to validate these active alerts, finds no history on them then triggers the alerts. The same can also occur on any active alert less than 30 days if the history was removed somehow.

Resolution

This issue is slated to be fixed within the next release.

 

 

 

 

Last modified

Tags

Classifications

Public
/*]]>*/