|
|
| Subject: | Architecture question - Possible for collectors to report to multiple front ends? |
| Author: | [Not Specified] |
| Posted: | 2014-04-04 10:42 |
Hiya,
We're currently on 3.2.1 core and looking at resilience and scalability. Hopefully moving to version 4.2.4 core soon.
We would like to have two collectors and one central zenoss - but then that provides a weak point in the resilience in that the central zenoss is necessary and if that goes down then we have no view of the network.
Is it possible to get the two collectors to report status and polls back up to two different Zenoss Systems at the same time With one as a Master node
I would just like to know if it's even possible!
Best regards,
Matt
| Subject: | Cluster |
| Author: | [Not Specified] |
| Posted: | 2014-04-04 12:15 |
I doubt there is a way to configure the collectors to report back to two different systems, but it shouldn't be very difficult to setup a cluster for the Zenoss Master using open source linux tools.
Here is an old post about it: http://community.zenoss.org/docs/DOC-2485
Do some research for your specific OS and see what clustering abilities it has.
Hydruid
| Subject: | Cluster |
| Author: | [Not Specified] |
| Posted: | 2014-04-11 05:27 |
Thanks for that Hydruid.
Looking into that now - I can see how to do it (although the proof of the pudding will be getting it working in our QA lab).
Another quick question though - can you do the same for the collectors Or have a spare collector doing nothing that can be automatically switched to if the live collector fails
| Subject: | Again clustering is the |
| Author: | [Not Specified] |
| Posted: | 2014-04-11 13:03 |
Again clustering is the answer!
Hydruid
| < |
Previous Creating device reports using zendmd |
Next zenoss memory report recipients |
> |