Gartner Market Guide for IT Infrastructure Monitoring Tools
GET THE GUIDE
The State of Machine Learning in 2019 - How Machine Learning Will Impact IT OpsGoogle and Zenoss bring contemporary applications of state-of-the-art AI and machine learning technologies to life.
Zenoss is the only enterprise monitoring solution certified Nutanix Ready - Integrated.
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
ON-DEMAND WEBCASTEmerging Trends With IT Monitoring Tools: Broader Collection of Data Types is Key to Pinpointing Issues
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
The ZenPacks.zenoss.DistributedCollector ZenPack allows you to deploy additional performance collection and event monitoring daemons, on the Zenoss platform master host, and on other hosts.
This feature allows you to:
When you first install Distributed Collector, Zenoss platform is configured with one hub and one collector. You cannot delete the initial hub and collector (each named localhost) that are set up by Distributed Collector.
A collector is a set of collection daemons, on the Zenoss platform server or another server, that shares a common configuration. That configuration contains values, such as:
Each collector has its own copy of each of the Zenoss platform collection daemons. For example, Zenoss platform initially contains collection daemons with names like zenperfsnmp, zenprocess, and zenping.
Distributed Collector also allows you to set up new hubs. A hub represents an instance of the zenhub daemon, through which all collector daemons communicate with the object and event databases.
All collectors must belong to exactly one hub; however, a hub can have many collectors associated with it. All hubs (and indirectly all collectors) refer to the same object and event databases. Typically, in Zenoss 4.x and up, only very large systems with more than five collectors (or more than 1,500 devices) benefit from multiple hubs. In 5.x and up, only one hub is recommended.
Hubs manage configuration data and pass it to the collectors. Hubs also take data from the collectors and pass it to the Zenoss DataStore.
For more documentation on using remote collectors, please see the Zenoss Service Dynamics Help Center
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.