The fourth milestone of Hawkular released

A blog post by Peter Palaga

hawkular | release

Hawkular, the monitoring platform, is happy to announce the release of its fourth milestone 1.0.0.Alpha4.

Improvements in Alerts definitions

Alerts are there to inform the user about an occurrence of a problem in some of the monitored resources. The present release adds some new configuration dialogs and improves the existing ones.

There are new configuration options to setup Alerts based on JVM Heap Usage and Garbage Collection.

JVM Alert Settings for Heap Usage
Figure 1. JVM Alert Settings for Heap Usage

There is a new dialog to configure Alerts for Datasources.

JVM Alert Settings for Datasources
Figure 2. JVM Alert Settings for Datasources

And there are new Specialized dialogs to configure Alerts for URLs' Availability and Response Time.

JVM Alert Settings for URLs' Availability
Figure 3. Settings for URLs' Availability

Red Hat Access Portal Integration

We added an integration with the Red Hat Access Portal to Hawkular. Users with valid Access Portal credentials are now able to browse the Knowledge Base, view and create Support Cases using the Hawkular user interface. On the future releases, we plan to improve this integration by adding more features. If that sounds interesting to you, we are looking forward for your feedback on #hawkular channel on Freenode.

Open a ticket on Red Hat Access portal using the Hawkular UI
Figure 4. Open a ticket on Red Hat Access portal using the Hawkular UI


While these changes in backend are not used by the UI yet, they present an important step towards a new UI functionality in future releases:

  • Hawkular Inventory now provides an API for configuration of resources and Hawkular Agent is using this API.

  • Hawkular Bus and Agent now support the execution of operations on any resource HAWKULAR-483.

  • Hawkular Bus offers a new infrastructure to stream large data from UI to monitored Application Servers. This is especially important for another feature that was added in the backend, namely the support for deploying applications on monitored Application Servers.

Other minor tweaks and fixes

  • HAWKULAR-488 - Display IP Address for Application Servers

  • HAWKULAR-254 - Blank screen on Windows

  • HAWKULAR-336 - Inconsistent time information on URL details page

  • HAWKULAR-406 - Same data for 2 different Wfly servers shown

  • HAWKULAR-494 - Datasources not unique per server

  • HAWKULAR-497 - Resources in inventory are lost at restart

  • HAWKULAR-521 - "" isn’t using the hawkular favicon.

  • HAWKULAR-526 - Downtime duration alert settings don’t persist after save.

  • HAWKULAR-536 - License Check of imported node_modules

  • HAWKULAR-553 - Url input is not validated (enough)

  • HAWKULAR-579 - "Alert Settings" link on URL details > All Alerts does notthing when clicked

Full list of Jira issues fixed in this release: Release Notes - Hawkular - Version 1.0.0.Alpha4

Watch the demo online


You can download the release here:

What’s next?

The next Alpha is planned for September 25th, and we are looking forward to work on the following features:

  • Deployment of new applications into managed servers

  • Definition of jdbc drivers and data sources

Published by Peter Palaga on 27 August 2015


© 2016 | Hawkular is released under Apache License v2.0