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 are not working after poller migration

Alerts are not working after poller migration

Created by William Muhle, last modified by Aileen de Lara_ret on Oct 04, 2016

Views: 920 Votes: 0 Revisions: 6


Resolution to the issue when alerts stop working after migrating the polling engines.  


Any NPM/Orion install that was upgraded from a pre 11.5 install at some point in time


If you had basic alerts set up prior to 11.5, your alerts were migrated into the new alerting based upon polling engines. The old basic alerts were tied to the pollers. And when you migrated the polling engine, the alerts did not migrate with it. Thus, they are still trying to alert only on the polling engine ID that they were originally tied to.


  1. Find the alert that is not firing off.
  2. Check the Trigger Condition tab.
  3. Look under the Scope of alert and see if you see something akin to the following:


  4. Either set the Polling Engine to the new poller, or put a tick mark in the radial button for All Objects In My                Environment.


Last modified