TECHZEN Zenoss User Community ARCHIVE  

Zenoss 5 Multiple Collectors

Subject: Zenoss 5 Multiple Collectors
Author: [Not Specified]
Posted: 2015-10-06 11:03

Hi,

Has anyone managed to set up working multiple collectors in Zenoss 5 I've been trying to make http://wiki.zenoss.org/Zenoss_Core_5_Scaling work, but it's not working for me.

The reason I'm trying to get extra collectors working is as I will need to scale at least 8000 hosts with a large number of zencommand checks. Historically we have had issues with saturation on our zencommand and zenmodeler clusters so I'm trying to beef things up.

Thanks!

Joan



Subject: Zenoss 5 core doesn't have
Author: Jan Garaj
Posted: 2015-10-06 18:01

Zenoss 5 core doesn't have concept of collectors (or at least no free remote collector zenpack at the moment).
Remote collectors are available only in enterprise Zenoss version. You can scale only number of "workers" (containers) in Zenoss Core, but I'm skeptic in your case (8k devices with zencommands).

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: Hi Jan,
Author: [Not Specified]
Posted: 2015-10-07 06:58

Hi Jan,

Thanks so much for the reply. I really really want to move from Zenoss 3.2.1 to Zenoss 5, but I'm finding it very hard to understand how scaling/collectors etc work in Zenoss 5.

Just before you replied, I found the section in control center where I can increase the number of instances of Zenoss running.
Are these the "workers" you refer to

Can you tell me exactly how Zenoss uses these Does it just share tasks amongst them as necessary
I mean, looking at it from Control Center, there's not a lot of visibility into it. I can see that there are 2 instances running, but it's still the same number of daemons/containers etc.. ie, I can still only see one instance of zencommand running..

What exactly is it adding

Thanks,
Joan



Subject: Dunno, you should to dig into
Author: Jan Garaj
Posted: 2015-10-07 07:10

Dunno, you should to dig into code - but you have some experience already http://www.zenoss.org/forum/135606

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



< Previous
[SOLVED] [Zenoss API] HTTP Error 503 on API updateNotification call - On call sc ...
  Next
Zenoss 5 Redundancy
>