Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > 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: 40 Votes: 0 Revisions: 6

Overview

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

Environment

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

Cause 

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.

Resolution

  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:

BasicAlert.PNG

  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
19:11, 3 Oct 2016

Tags

Classifications

Public