given the recent discussion about the backend we should be using for
inventory, I've quickly put together a brief explanation of what inventory
actually stores and how it queries things.
This is expected to raise more questions than to provide answers though and is
meant as a starter for the discussion that I hope will happen in the comments
section of the google doc .
I was testing a little bit with Hawkular-Services + Cassandra cluster
using docker containers, I created a GitHub repository with my setup:
It seems to work fine, at least on my environment, I did some different
tests but I couldn't test more than 3 nodes on my machine, but hopefully
it will work for N nodes.
Some issues I found:
- Sometimes hawkular throws a timeout exception "Cassandra timeout
during read query at consistency LOCAL_ONE", I only managed to reproduce
it 2 times.
- This setup is not enough robust because the Keyspace has replica
factor of 1, so if one node dies hawkular-services started complain
There is a concern that the Hawkular WildFly Agent is bloated with stuff people aren't really using or are going to use and is going to make maintaining it more complicated than it needs to be.
So I want to get feedback on the following plan. This is being tracked in JIRA here: https://issues.jboss.org/browse/HWKAGENT-142
We are going to take out support for JMX/Joloxia and Prometheus managed endpoints. The agent will only support collecting metrics from "DMR endpoints" (that means WildFly Servers - either in standalone or domain mode).
Rather than lose the code for the JMX/Jolokia and Prometheus support, we are going to fork master into a separate branch. If we ever do need to resurrect that code, or someone wants to build an agent with those features to play around with, we'd have that branch available.
I was looking at how to find all tags in the metrics system
and found endpoints like
(similar exist for Counters, avail, ...)
Those expect a "tag-query". With some looking at the source and trying
I found out that app:* works, but not *:cpu or even *:* to find all tags.
Do metrics-only users completely rely on external orchestration to find
Now with pets vs cattle and containers coming and going, we need those
labels to identify what belongs together.
For Hawkular-services, how will we store those tags in a way that
clients (e.g. ManageIQ) can find them and thus also query metrics for
The Hawkular Alerting team is happy to announce the release of Hawkular
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
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
o A refactor to simplify action plugins by unifying on one type of
* [HWKALERTS-164] - Simplify Alert.resolvedTime and Alert.ackTime with
o More powerful life-cycle handling, allowing more status
transitions for a single alert, and an easily accessible list of
* [HWKALERTS-165] - Refactor hawkular-alerts-rest to support several
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:
Hawkular Alerting Team
Jay Shaughnessy (jshaughn(a)redhat.com)
Lucas Ponce (lponce(a)redhat.com)
Hey Hawkular Folk,
So I just wanted to know what is the ‘the way’ to incorporate branches or PRs that one’s branch is dependent on? Since merging into MiQ master takes so long, what is our strategy around dependent merges? We are unfortunately in the realm of long lived branches now. Much more rebasing and conflicts given the extended timeframes for merging.
I have asked around, and no one is confident in “the way”.
I have a couple methods in mind but not sure what the best practices are…. Please speak up if one works for you and we can adopt it.
we have released hawkular-services 0.14.
Changes to 0.13 are
* Agent has been updated to v 0.22
* Inventory has been updated to 0.19.2: this has a different backend
than before, so hammer it :)
Unofficial Docker images are available as follows:
* pilhuhn/hawkfly (0.22.0)
* pilhuhn/hawkfly-domain as a WildFly in domain mode.
Thanks to everyone who has contributed to this and all the previous