The Hawkular Alerting team is happy to announce the release of Hawkular
Alerting 1.2.0.Final.
This is a feature and fix release.
* [HWKALERTS-160] - CompareCondition can not require both DataIds to
be supplied for the same engine firing
o This makes CompareCondition more useful and predictable by
removing the restriction that both metrics [used in the
comparison] be reported at the same time.
* [HWKALERTS-161] - Extend alerts criteria to support resolved and ack
timestamps
o More powerful querying around life-cycle changes.
* [HWKALERTS-162] - Allow to not store external events
o EventConditions can now be evaluated using transient
(unpersisted) events. This prevents unnecessary storage of
events meant only for trigger condition evaluation.
* [HWKALERTS-163] - Unify actions architecture under a single
implementation
o A refactor to simplify action plugins by unifying on one type of
plugin registration.
* [HWKALERTS-164] - Simplify Alert.resolvedTime and Alert.ackTime with
Alert.lifecycle
o More powerful life-cycle handling, allowing more status
transitions for a single alert, and an easily accessible list of
status changes.
* [HWKALERTS-165] - Refactor hawkular-alerts-rest to support several
artifacts
o A refactor to provide artifacts for both standalone and Hawkular
Services. Starting with this release the different artifact
flavors are all published.
* [HWKALERTS-166] - CassCluster needs to detect schema is fully
created on multi nodes environments
o A stability enhancement for clustered deployments, to ensure the
Cassandra schema is ready for all nodes.
* Hawkular Metrics embeds Alerting!
o V1.2.0.Final is the base version for embedded alerting in
Hawkular Metrics! Coming Soon!
For more details for this release:
http://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12315924&ve...
Hawkular Alerting Team
Jay Shaughnessy (jshaughn(a)redhat.com)
Lucas Ponce (lponce(a)redhat.com)