Resource Manager provides self-monitoring capabilities. A visual pipeline-based status page in the browser interface shows an overview of the monitored Resource Manager instance, including key metrics for nodes in the metric collection, event generation, and modeling processes.
Use data to troubleshoot performance issues with Resource Manager components and proactively manage performance. For example, data can help you determine when a component or service in the system is overloaded. Before issues occur, optimize system performance by adding more instances, more memory, more CPU, or adjusting configuration settings.
You can add custom events and custom thresholds, and edit shipped thresholds for components that have them.
For more information see the "Monitoring Resource Manager health and performance" chapter in the Zenoss Resource Manager Administration Guide.
Solr model catalog
The deprecated catalogs have been replaced by adapters that mimic the legacy catalogs' interfaces and use Model Catalog under the hood, so that current ZenPacks should function without any changes. However, there could be cases where ZenPacks use the legacy catalogs in a way the adapters do not support. In such cases, either the adapter or the ZenPack would need to be modified.
There have been many improvements to the graphing functionality including the ability to configure a default time range and number of columns, and clicking within a graph to zoom in and re-center the graph. For more information, see the Zenoss Resource Manager Administration Guide.
Expanded logging and improved management of audit logs
Audit logging has been expanded to include Control Center configuration and service changes. This audit log can be found at /var/log/serviced/serviced-audit.log. There have also been improvements in the ability to configure the retention period for audit logs to be different than that of other logs.
Preserving metrics when reidentifying a device
Clustering of collector Redis
This enhancement increases the efficiency of multi-host collectors by ensuring that cached collector configurations are effectively used between collector Redis restarts. The number of collector Redis instances must be equal to the number of collector hosts in the pool, and the host pool DFS access must be turned off.