Hawkular Metrics + Hawkular Alerts - Phase 0
by Stefan Negrea
Hello Everybody,
I want to open the discussion around the design and implementation for the Hawkular Metrics and Hawkular Alerts integration. I created a document with the scope and objectives for Phase 0. It is called Phase 0 because this should be a proof of concept of the type of functionality to be delivered in the future with a scope of getting early feedback on our ideas. The goal is to deliver this phase in Hawkular Metrics 0.10.0, and have something implemented in the next 2 weeks.
I've had discussions with developers on both teams and updated the document based on those discussions. My goal was to first refine the ideas to a coherent state before publishing a first draft. I am now opening the document and the discussion to the entire Hawkular community.
The one point where we need additional help is highlighted in red with a bigger font in the document.
Please feel free to comment in the document, reply to this email, or contact me (stefan_n) on #hawkular on freenode. If you do not have access to the document please email me privately and will grant access. Any and all the feedback is more than welcomed.
Link: https://docs.google.com/document/d/1PwOGGysO0ppc2VPl80i4ye9pZI-Ugd4gObzQ5...
Thank you,
Stefan Negrea
Software Engineer
10 years, 1 month
REST-api and hyperlinks
by Heiko W.Rupp
Hey,
one cool trait of RESTful apis, which we all use every day hundreds of times
is the hyperlinking of data - we click on links in the web browser.
I think that would be pretty good for our apis as well.
To take alerts as an example (see my other mail)
I can go like GET /triggers/{id} to get a trigger with some data.
Now to learn about the conditions I need to browse to the docs
to potentially find out that I can get them at /triggers/{id}/conditions
It would be good if we would add for each resource a "Links" section
like:
links: [
{
rel='dampening'
href=http://blabla/hawkular/alerts/triggers/{id}/dampening
},
{
rel='conditions'
href=http://blabla/hawkular/alerts/triggers/{id}/conditions
}
]
This way it is relatively easy to follow those for humans, but also
machines.
10 years, 1 month
[Alerts] trigger comparator in one go?
by Heiko W.Rupp
Hey,
when I call GET /triggers or GET /triggers/{id}
I get a hash with basically this information:
http://www.hawkular.org/docs/rest/rest-alerts.html#Trigger
Inside the context I have the resource it triggers on, the metric
it triggers on, the triggerType, but not the comparator or the value to
compare.
Looks like I need to get /triggers/{id}/conditions and also /dampenings
separately to get those values
Is there an api call / parameter, where I can get all data for a single
trigger including dampening, conditions and so on ?
10 years, 1 month
-SRC- deps and releases
by John Mazzitelli
I need to release agent prior to this big refactoring going in master. So I'm trying to get that done tonight.
Also, Tristan is doing work with the agent and needs to pull it in but getting errors.
https://gist.github.com/tristantarrant/f20de03390acc15d663b
Notice the failure to resolve the -SRC- dependency: "failed to resolve artifact org.hawkular.cmdgw:hawkular-command-gateway-api:jar:0.10.2.Final-SRC-revision-06aa579bd1b9658cf82af6cfedef6365ecf03e8c: Could not find artifact org.hawkular.cmdgw:hawkular-command-gateway-api:jar:0.10.2.Final-SRC-revision-06aa579bd1b9658cf82af6cfedef6365ecf03e8c in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/)"
I actually got rid of that dep, however, I need inventory 0.8.0.Final and that isn't released yet. So my agent only has a -SRC- dep on it.
But if I release agent with a -SRC- dep in it, will that be consumable by someone outside of hawkular?
If this is going to be a problem, is it possible to get an inventory release out ASAP so I can get agent released without -SRC- dep?
10 years, 1 month
nest circular dep
by John Mazzitelli
Well, I found the nest dependency circularity that I was sure was around :)
hawkular-agent has itests that builds a distro using nest. But you can't get the nest until you build kettle. And you can't build kettle until you build the agent. And 'round and 'round we go.
We need to pull the nest out of kettle and put it somewhere else. For now, I'm just going to have a dependency on an older bus version to pick up the nest.
10 years, 1 month
