Zenoss Core Changelog

What's new in Zenoss Core 3.0.3

Oct 28, 2010
  • The VMWare Infrastructure ESX Server ZenPack allows you to monitor ESX hosts and guests via VMWares EsxTop utility.
  • Improved scalability and performance with the following defects closed: http://tinyurl.com/28eh3uf
  • Documentation has been updated for 3.0.3, specifically theZenoss Installation Guide, Zenoss Developer's Guide, Zenoss Extended Monitoring, Zenoss Source and JSON API Documentation. The installation guides have been enhanced to cover more detailed information about system requirements, and contain some recommended performance settings for a few key configuration files
  • TheVirtual Host Monitor ZenPack has been updated.
  • The Global Device Search Core ZenPack is available for installation, providing search by hostname or IP with support for wildcards.

New in Zenoss Core 3.0.2 (Sep 15, 2010)

  • Completely redesigned user interface designed to improve operational effectiveness through simplified naviga- tion, redesigned pages, and embedded tooltips and page tips.
  • Expanded integration and customization through new REST API. In addition to its scriptable command line interface, interactive shell, and expansive Web services API based on XML-RPC, Zenoss now offers a REST API with easily consumable XML or JSON return formats. The benefit to end users is more flexible and simplified options for customization and rapid integration with other management tools.
  • New search facility (accessed from the Infrastructure page) allows simultaneous substring search on device names, IP addresses, and device classes.
  • Product documentation in EPUB e-book format. You can read EPUB books from your iPhone, iPad, Sony Read- er, or Nook, or by using e-reader software such as Stanza, FBReader (for Linux devices), or the EPUBReader plugin (for Firefox users).
  • Upgraded versions of Python (2.6) and Zope (2.12).
  • Reliability and availability improvements.

New in Zenoss Core 3.0.1.784 (Sep 15, 2010)

  • Completely redesigned user interface designed to improve operational effectiveness through simplified naviga- tion, redesigned pages, and embedded tooltips and page tips.
  • Expanded integration and customization through new REST API. In addition to its scriptable command line interface, interactive shell, and expansive Web services API based on XML-RPC, Zenoss now offers a REST API with easily consumable XML or JSON return formats. The benefit to end users is more flexible and simplified options for customization and rapid integration with other management tools.
  • New search facility (accessed from the Infrastructure page) allows simultaneous substring search on device names, IP addresses, and device classes.
  • Product documentation in EPUB e-book format. You can read EPUB books from your iPhone, iPad, Sony Read- er, or Nook, or by using e-reader software such as Stanza, FBReader (for Linux devices), or the EPUBReader plugin (for Firefox users).
  • Upgraded versions of Python (2.6) and Zope (2.12).
  • Reliability and availability improvements.

New in Zenoss Core 2.5.2 (Mar 4, 2010)

  • Improved reliability and performance, with a focus on the new event console introduced in the prior version.
  • A new Xen Virtual Hosts ZenPack for monitoring Xen para-virtualized domains and their guests.
  • More than 50 new ZenPacks (contributed by the community since Version 2.4)

New in Zenoss Core 2.5.0 (Oct 28, 2009)

  • A newly redesigned Event Console offers inline event filtering and improved usability. A new "Event Details"
  • pane helps streamline troubleshooting tasks.
  • A new Community Site Window Portlet that provides easy access to Zenoss information resources.
  • The Amazon Web Services™ ZenPack, which allows you to monitor the performance and availability of
  • Amazon Elastic Compute Cloud™ (Amazon EC2™) Web services.
  • More than 40 new ZenPacks (contributed by the community since Version 2.4)

New in Zenoss Core 2.4.5 (Sep 2, 2009)

  • Zenoss Setup Wizard, which guides you through initial system configuration and device addition.
  • Additional, simplified method for adding devices.
  • Ability to implement remote SSH monitoring (requires ZenPack creation following provided example).
  • Reporting normalization.
  • Over 100 community-contributed ZenPacks.
  • Expanded documentation, including the Zenoss Extended Monitoring guide.

New in Zenoss Core 2.4.1 (May 14, 2009)

  • Zenoss Setup Wizard, which guides you through initial system configuration and device addition.
  • Additional, simplified method for adding devices.
  • Ability to implement remote SSH monitoring (requires ZenPack creation following provided example information).
  • Reporting normalization.
  • Over 70 community-contributed ZenPacks .
  • Expanded documentation, including the Zenoss Extended Monitoring guide.

New in Zenoss Core 2.4.0 (May 6, 2009)

  • Zenoss Setup Wizard, which guides you through initial system configuration and device addition.
  • Additional, simplified method for adding devices.
  • Ability to implement remote SSH monitoring (requires ZenPack creation following provided example information).
  • Reporting normalization.
  • Over 70 community-contributed ZenPacks.
  • Expanded documentation, including the Zenoss Extended Monitoring guide.

New in Zenoss Core 2.3.3 (Feb 24, 2009)

  • For Enterprise customers, Zenoss now offers the WebsphereMonitor ZenPack, which comprises a basic Websphere template and zProperties for Websphere monitoring.
  • The Enterprise ZenWebTx ZenPack now supports extracting data from XML documents by using xpath queries.
  • For Enterprise customers, Zenoss now provides comprehensive monitoring of your VMware infrastructure.
  • It collects performance data from VMware servers (hosts), virtual machines (guests), VMware clusters and VMware data stores. By monitoring the entire VMware stack, Zenoss provides a complete picture into VMware's performance and availability, allowing you to quickly monitor and troubleshoot VMware-related problems.
  • Zenoss expands your ability to monitor Java applications with improved JMX monitoring and error reporting. Zenoss also can receive JMX events that are sent from JMX applications.
  • This version of Zenoss also provides improvements to monitoring the performance and availability of Windows servers. It collects data by using Windows Management Instrumentation (WMI) and Windows Perfmon.
  • Zenoss offers an expanded list of ZenPacks for download, including more than 50 community-contributed monitoring ZenPacks.

New in Zenoss Core 2.3.2 (Dec 18, 2008)

  • New:
  • For Enterprise customers, Zenoss now provides comprehensive monitoring of your VMware infrastructure. It collects performance data from VMware servers (hosts), virtual machines (guests), VMware clusters and VMware data stores. By monitoring the entire VMware stack, Zenoss provides a complete picture into VMware's performance and availability, allowing you to quickly troubleshoot VMware-related problems.
  • Zenoss expands your ability to monitor Java applications with improved JMX monitoring and error reporting. Zenoss also can receive JMX events that are sent from JMX applications.
  • This version of Zenoss also provides improvements to monitoring the performance and availability of Windows servers. It collects data by using Windows Management Instrumentation (WMI) and Windows Perfmon.
  • Zenoss offers an expanded list of ZenPacks for download, including 30 community-contributed monitoring ZenPacks.
  • Fixes:
  • Add better error handling to zenpatch.
  • SNMP v1 traps have a 0 (zero) inserted into them.
  • zenping needs to reload its config if it defers loading its config.
  • DifferentiateTemplates migrate step skips templates with a targetPythonClass set.
  • Listen IP address should be configurable for zensyslog and zentrap.
  • A traceback error is generated when a Linux device is modeled under the /Server/Cmd class.
  • Logic to update pickle files is flawed, leading to outdated information read by zenperfsnmp on start.
  • Missing init .py files for Modelers.
  • The zenrender daemon does not send heartbeats.
  • Do not allow creation of a user named "user."
  • User interface implies monitoring of UDP services is possible.
  • zenpop3 fails when using SSL.
  • Legend on threshold graph points is imprecise.
  • Event console doesn't update.
  • zenmodeler collects all devices (rather than the single device assigned to the collector).
  • Alert message must use field in body to appear in clear body.
  • Some vendors require that a .0 be inserted between the enterprise and specific OIDs in V1 traps.