Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > 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: 54 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
21:43, 22 Jun 2016

Tags

Classifications

Public