Hyperic HQ 3.2
Commando*/Version 3.2 (Jan 2008)
* No, it's not what you think. The theme is Schwarzenegger movies.
Open Source Features Targeted for the Commando Release
| Feature Name | Description | Why This Is Useful |
|---|---|---|
| Scalability Improvements | Several improvements are included in this feature:
|
Who doesn't like faster, more reliable, and more consistent performance? |
| MySQL Database Support | Full support for MySQL database to be used as backend data store for HQ, leveraging the proliferation of MySQL in the enterprise and existing DBA expertise. The performance of MySQL is expected to be on par with the other backend databases we currently support: Oracle and Postgres. | Administrators now have more flexibility in their choice of backend databases for HQ — Postgres, Oracle, or MySQL — and can choose the one that best suits their system overall. |
| Improved Nagios (R) Integration/Nagios Migration Utility | The HQ plugin for Nagios is substantially improved. Importing of Nagios hosts, commands and service objects is automated. HQ has the ability to run Nagios plugins natively and view Nagios Services, Hosts, and Statuses in a way that is identical to the Nagios Service Details interface. | Users can now integrate Nagios seamlessly and completely into HQ, enabling them to use only one tool, HQ, to manage their systems. |
| Live Data | This feature allows HQ users to view — in real time — performance data for a single platform or across a number of platforms, in a rich, centralized user interface. The Live Data framework is built on Hyperic's own OS-independent SIGAR libraries, which means that commands can be executed on both Windows and *nix systems. Executable commands include:
|
Network administrators can now see the standard information they most want about any network hosts simply and in real time, complementing the metrics displays and reports already available in the UI. This allows for quick and easy troubleshooting of a troublesome host. |
| Currently Down Resources (Quick Look Screen) | This screen gives users, at a glance, a view of all down resources and how long they've been down. The view can be narrowed by type, either by inventory level (plaform, server, or service) or by resource type (for example, Linux or Apache). It can also be sorted by resource name, type, the time the resource went down, and length of down time. | Having a list of all the unavailable resources in a single screen tells users whether all resources are available or not, whether alerts are firing for applications or resources because the platform that these services live on is down, and how long resources have been down. Armed with this information, the user can more easily figure out how to fix the problem. |
| Global Alert Disable/Planned Outages | The HQ Administrator can globally disable all alerts on-demand. | For planned maintenance or outages, Administrators can disable all HQ alerts globally, to prevent unwanted alerts from being generated during the system down time. |