Hi Thwacksters,
Has anyone dealt with an environment where there are over 100 Orion web console users that access the monitoring platform (inclusive of NPM, NTA, NCM, VNQM, IPAM, UDT, SAM, WPM, SRM & DPA) ?
The users are segregated as Network, Server, Application, DB and Platform users. Each of the teams has separate users that need to monitor their respective devices.
We have split the users amongst 2 web servers - one sitting on the main platform and an Additional Web server. The main platform does not run the SQL DB services - the Orion database has been built on a separate server.
We observe that the CPU utilization on the core Orion platform reaches 100% very frequently. We are required to Stop and restart the Orion services frequently to get the CPU utilization down.
It maybe noted that we have followed the best practices in terms of providing more than the recommended CPU, RAM, Disk IOPS for the Core platform, the database server as well as the Additional web server not to forget the 6 Additional Polling engines.
Any pointers to articles that may help us design a better Web Access mechanism to the Orion monitoring are most welcome.
regards