Missed runs are actionable
(ZEN-25765) Collector daemons regularly initiate the "stats" process as part of the maintenance cycle. The daemon log contains detailed information about collection task status; for example, which devices have missed runs. Missed runs for devices are listed as INFO events in the EVENTS console. To see where a missed run occurred, view the event details. If necessary, take action to resolve the issue, such as restarting zenpython.
Viewing devices and events
(ZEN-29263) The browser interface provides consistency between devices and events for those devices. Users can see devices for all /System organizers and events for those devices in the sub-organizers under /System.
Configurable service restart thresholds
(CC-4100, ZEN-17361) You can use a new feature in Control Center, restart thresholds, to manage services. Edit the service to specify a value in the new field Restart when memory usage exceeds % of requested RAM. When your threshold is reached, the service restarts automatically.
For example, if Zope is configured to use 400mB of RAM and its restart threshold is 90%, each instance of that service will be restarted when the service consumes 360mB.
ZenPacks no longer rely on Nagios plugins
Collector Redis cluster
A recent enhancement allows you to cluster the Redis caching service (collectorredis) in collector pools. Clustering increases the efficiency of multi-host collectors by ensuring that cached configurations are used effectively between collectorredis restarts.
For more information, refer to the Zenoss Resource Manager Configuration Guide.