<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
We're happy to announce 0.3.0.Final of Hawkular Alerts. A bunch of
good stuff this time around, here are the relevant Jiras and a few
highlight blurbs:<br>
<font face="Calibri"> <br>
** Enhancement<br>
* [HWKALERTS-17] - Refactor to eliminate EE dependencies of
EJB3<br>
<br>
Now packaged as a WAR as opposed to an EAR, for easier
consumption in another EAR.<br>
<br>
* [HWKALERTS-50] - Integrate with Hawkular Metrics<br>
<br>
A value-add External Alerter deployment (WAR) that adds more
alerting power when integrated with Hawkular Metrics. Thanks to
John Sanda for his help.<br>
<br>
* [HWKALERTS-52] - Hooks for external alerts<br>
<br>
A mechanism for integrating External Alerters into Hawkular
Alerts. Allows external clients to leverage the Hawkular Alerts
Trigger and Action infrastructure.<br>
<br>
* [HWKALERTS-57] - Improve the way actions plugins access
information related to an alert<br>
<br>
Now Actions and Notifiers have full access (via JSON) to the
Alert details.<br>
<br>
* [HWKALERTS-59] - Review if 204 return code can be changed to
an empty list<br>
<br>
API CHANGE! Get Alerts now returns and empty list as opposed
to 204 when the criteria results in in no alerts.<br>
<br>
* [HWKALERTS-60] - Review end point for alert resolution<br>
<br>
New REST endpoints for Ack or Resolve of a single alert.<br>
<br>
* [HWKALERTS-62] - Allow any data to store contextual
information<br>
<br>
Optionally Store a Map of context data with any datum sent
into alerts for evaluation. Then use that context info in your
actions.<br>
<br>
* [HWKALERTS-65] - Adapt email plugin to support multiple
conditions and multiple states<br>
<br>
Big enhancements in e-mail notifier for rich messages at
different life-cycle points.<br>
<br>
* [HWKALERTS-67] - Update gson dependencies with jackson<br>
<br>
Remove use of GSON, now depends on fasterxml provided by
Wildfly.<br>
<br>
** Feature Request<br>
* [HWKALERTS-64] - Enable trigger on alert resolution<br>
<br>
- Now can AutoEnable an [Auto]Disabled Trigger when its alerts
are resolved. <br>
- Now automatically returns an AutoResolve Trigger to firing
mode when its alerts are manually resolved.<br>
<br>
<br>
Please contact us with any questions, comments or contributions!<br>
<br>
Jay Shaughnessy (<a class="moz-txt-link-abbreviated" href="mailto:jshaughn@redhat.com">jshaughn@redhat.com</a>)<br>
Lucas Ponce (<a class="moz-txt-link-abbreviated" href="mailto:lponce@redhat.com">lponce@redhat.com</a>)<br>
<br>
</font><br>
</body>
</html>