Why Separate Monitors and Data Collectors for ControlUp?

It is important to separate Monitors from Data Collectors in order to avoid competing for resources as well as breaking up extensions into chunks. Many companies opt for 8 Data Collectors, while some run Data Collector on Monitor servers if there is no sizing issue. Further resources concerning Data Collectors can be found at ControlUp’s blog article and KB page (https://www.controlup.com/resources/blog/entry/what-is-a-data-collector-and-why-does-it-matter, https://support.controlup.com/docs/controlup-data-collector).

Read the entire ‘Why Separate Monitors and Data Collectors for ControlUp?’ thread below:

doing up a document what is the main reasons for separating Monitors and Data collectors?

Load. You don’t want to compete for resources with a fully loaded 8×32 monitor.

Damn it Landon

Also if you have a ton of extensions you want to break them off in chunks.

Say you have like 40 NetScalers. Break that up across a handful of data collectors.thats what i was putting but wanted to make sure not missing anything

lol 40 netscalers hehe don’t think any company in ireland would have that manhyI’ve run into a couple with that many. Crazy but they are out there.

8 was the most i seen

SDX running lots of VPX is not that uncommon…

I know a guy who ran Data Collector on Monitor servers very successful if there is no sizing issue!

As soon as there is a little peak in CPU and/or Memory and cuAgent and cuMonitor are starting to battling you are screwed 🙂

Learned it the hard way. Better separate those services.

Regarding Data Collcetor I recommend Joel’s Blog post and the KB:

https://www.controlup.com/resources/blog/entry/what-is-a-data-collector-and-why-does-it-matter/

https://support.controlup.com/docs/controlup-data-collector

Continue reading and comment on the thread ‘Why Separate Monitors and Data Collectors for ControlUp?’.  Not a member? Join Here!