2 Replies Latest reply on Feb 18, 2014 2:33 PM by sean.martinez

    Assigning Alerts to an Additional Poller in NPM 10.1.2


      Hi all,


      i have installed the additional poller in NPM 10.1.2 but i am having difficulty in assigning my existing alerts to the poller engine. I am following the administrators guide for NPM 10.1.2 and I have got to the point where I have made a copy of the alerts that I want to be assigned to the new poller, I have made a note iof the engine ID and now I need to run the SQL query.


      However the table that the sql query refer's to "Alerts", does not contain all the advanced alerts that I have created using the Advanced Alerting Manager. The table that contains my alerts is "Alert Definitions". But that table does not have a field for "Engine ID". So how do I run this query?


      has anyone come accross this before?





        • Re: Assigning Alerts to an Additional Poller in NPM 10.1.2

          Did you ever hear back on this?

          Running into the same issue here.

            • Re: Assigning Alerts to an Additional Poller in NPM 10.1.2

              Basic Alerts are tied to each Polling engine and have to be modified on each Polling Engine separately. Basic Alerts are contained in the Alerts Table and have EngineID to specify which Polling Engine they are assigned to. You would need to make a copy for each Basic Alert to assign them to every polling engine, then assign the EngineID to corresponding Poller out of the Engines Table.


              Advanced Alerts are designed in a way that instead of checking the Services on each system, they perform SQL Queries against the database and apply to all polling data regardless of the polling engines. Advanced Alerts can also only be configured on the Main Polling Engine as this is the only engine that contains the Alerting Service.