2 Replies Latest reply on Sep 2, 2015 9:17 PM by indera

    Sizing for centralize monitoring




      Good day!


      need help on the sizing for centralize monitoring the remote site. our monitoring team is reside on different region and we are monitoring the clients in Europe. since the primary poller already in different region, we plan to add additional poller engine in Europe. this will reduce the traffic load whereby all the client will not directly connected to the primary poller.


      question is, for the database, do we need to have different database for each poller? or we can use the same database for the primary and additional polling engine? the solution that im looking at is NPM, NTA, Storage resource Manager, SAM and DPA.


      Thanks in advance




        • Re: Sizing for centralize monitoring

          When you use additional polling engines, all the data collected by all the polling engines is written to the same MS SQL database. This would apply to NPM, NTA, SRM and SAM. NTA also uses an additional database called FSDB (Flow Storage DB), which is also used by all the polling engines.


          DPA would be a separate install. If the latency between DPA server and the databases isn't bad, you can monitor it from a central DPA server. If not, you can install multiple DPA servers, and activate parts of the DPA license on each DPA Server. DPA comes inbuilt with a feature called DPA Central that allows you to centrally view the data collected by multiple DPA servers.

            • Re: Sizing for centralize monitoring

              Thanks for the reply. since the primary and Additional polling engine will use the same database,  will it impact the performance of the database? let say i have about 2000 devices that need to be monitor, will it impact the performance? since it is recommended that the polling engine only manage 10k component, will it apply to the database as well? will it consume much bandwidth for additional polling engine to communicate with the database?