With the release of Hyperic HQ 3.2.2, we introduced a new piece that makes HQ infinitely more hackable: HQU. HQU lets you talk directly to the HQ engine, set up automated tasks, integrate with web services, and a lot more. Need to integrate your monitoring system with an XML feed? HQU lets you do that in minutes. Need to pull monitoring data and export it to another application or service? Easy. Will full access to the HQ API's and metric data from your monitored applications, HQU is the next stage in system and application monitoring. There's a full Groovy API, so adding more functionality to HQ is a snap. For this first release, we've created the Event Center plugin, which allows admins to view their log file data in a central location. See http://www.hquplugins.org/ and the HQU Documentation for more information and to access the first snippets of code. To download Hyperic HQ: http://www.hyperic.com/downloads/ Also, Jon Travis, Principal Engineer at Hyperic, did a webcast on using HQU: http://download.hyperic.com/swf/HyperCAST11/playback.html
- Posted by: John Mark Walker
- Posted on: March 31 2008 14:46 EDT
- Re: Introducing HQU - a Groovy-based UI plugin framework by Roy Russo on March 31 2008 15:25 EDT
- Groovy - Perfect for Java integration by Jon Travis on March 31 2008 19:00 EDT
Congrats to the Hyperic team! I had a chance to take a private tour of the offering while in SF, and was very impressed at the speed and depth of innovation. Roy Russo http://www.loopfuse.com
Our application comes from legacy frameworks -- J2EE session / entity beans, struts, JBoss MDBs, etc. This means that our core backend API has typically not been attractive to developers -- something that's very important to anyone wanting to tweak, script, or integrate their monitoring application with the rest of their environment (aka every sysadmin). So what does Groovy do for us? By using Categories and MetaClasses, HQU is able to provide an API that is easy to read, easy to write, and behaves in an obvious way. Of course it does not provide a 100% replacement for our backend APIs, which is another great reason to use Groovy -- it seamlessly interacts with the rest of our Java app. Groovy also makes development infinitely easier. Since we're able to develop features, test HQL queries, etc. inside of a _running_ application, the time between code-revs is very quick (hit reload. Done.) We have made a commitment to Groovy and will be using it more and more in subsequent releases. The release of the HQU framework means that the community now has more hooks than ever into a powerful infrastructure management application to create custom, centralized screens, specific to their environment.