
Release Notes for Zenoss Ser-
vice Dynamics Version 4.1.1
10
1.4.2.5. Internet Explorer 9
When using Internet Explorer 9, Resource Manager user interface page elements may not load and display
correctly. To work around this issue, go to the Internet Options Advanced tab (from Settings > Internet Options),
and then reset Internet Explorer settings.
1.4.2.6. Reports
After upgrade, reports may not display correctly for users with no assigned roles. (Internal Defect 28822)
To work around this issue, re-index the catalog with the command:
zencatalog --reindex
1.4.2.7. Windows Services
Resource Manager displays a status of "unknown" for Windows services that are disabled or not monitored.
(Defect 27028)
1.4.2.8. Zenoss Global Dashboard
Zenoss Global Dashboard is not supported in this release. If you are running Zenoss Global Dashboard, you
must contact Support before upgrading.
1.4.2.9. Collector Performance Graphs
Collector default performance graphs for cycle times show NaN values for zenping, zenperfsnmp, and zenstatus
daemons. (Internal Defect 29378)
1.5. Global Operations Management
This section lists updates and fixes for Version 1.0.2 of Service Dynamics Global Operations Management.
1.5.1. New Features
In this version, the HTTP client used to propagate actions to local and remote Resource Manager instances has
been rewritten for performance and reliability (using asynchronous I/O instead of threading).
1.5.2. Defect Fixes
Fixes in this version of Global Operations Management are:
• Properly timeout HTTP connections to local / remote Zenoss instances. Previously, zengomd could fail to
shutdown if a thread was blocked waiting for a response from a HTTP request.
• Removed an unnecessary logged exception in event.log when a target queue didn't exist on a GOM source
system.
• Fix GOM criteria filter to properly support filtering events based on the event count.
• Fix GOM criteria filter to properly handle 'contains' criteria on device organizers (Groups/Systems).
• Do not fail if a note cannot be propagated to an event on a source or target system if the event no longer
exists.
• Fix error when 'Update Model' preference is enabled for a source and an event class doesn't exist on the
target system.
• Avoid unnecessary object creation if 'Update Model' preference is enabled.
• Work around ConflictError when creating model elements when the 'Update Model' preference is enabled.
• Optimize the query used to search for existing devices when creating model elements.
• Set the title of created devices to the title from the forwarded event if 'Update Model' is enabled.
Kommentare zu diesen Handbüchern