Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Profiler poller sizing guidelines

Can anyone tell me what the best practices are in terms of having enough pollers for our Profiler deployment?

Our test deployment has so far been running as the sole poller and seems to be struggling with the systems which are currently being monitored. Often we are finding that performance statistics for a VMware solution is stopping and it takes a stop and start to get the stats coming back again.

We plan to monitor 2 more Vmware deployments as well as several EVAs and file servers etc so if there was a reference guide as to how many of certain types of monitors each poller should be handling it would be extremely useful. Can't seem to find anything about it in the Admin guide or Installation guide.

Thanks in advance!

Find more posts tagged with

scalability

profiler

Accepted answers

bmrad

For the Profiler Server, I would recommend a 2 processor 4GB server if you can offload the monitoring of the arrays, switches and Virtualization to 2 agents (a virtual machine is fine). You can leverage any of the agents you deploy to the backup server or file servers to monitor your storage arrays and switches. For the VM environment, you are limited to the number of pollers licenses you have - you start with 1, but can buy more. The poller license(s) can be applied to any agent, then it can monitor vmware.

If you need the Profiler server to do a majority of the work, I would beef up the memory to 6GB and use 64bit windows.

Brian

All comments

bmrad

How many arrays (and types) and how many VM are you monitoring?

Are they geographically separated?

Brian

Dunfraggin

We will be monitoring 4 HP EVA and 1 P4000 SANs and in total, around 300 VMs. In addition to this we are also looking to monitor 10 fibre switches, 12 file servers and a Backup Exec CAS deployment too. Later we plan to add our SQL farm too which currently sits at 8 SQL instances.

All of these systems are located within the same datacentre with the exception of 1 VMware deployment which is across a WAN link (25Mb MPLS) which is only hosting 12 VMs at present.

bmrad

If you need the Profiler server to do a majority of the work, I would beef up the memory to 6GB and use 64bit windows.

Brian