5:26 p.m.
Hi everyone,
I’m trying to use Hawkular API with AeroGear for Android.
Just to remind everyone, the Hawkular Alerts API uses HTTP PUT requests for actions such
as resolve and acknowledge. Affected alert IDs are passed as a HTTP query parameter. As
such, if I want to resolve an alert with ID “oops”, I need to do the following request:
http PUT :8080/hawkular/alerts/resolve?alertIds=oops
At the same time, AeroGear uses PUT requests more traditionally, appending model ID to the
request URL so it looks something like “hawkular/alerts/resolve/oops”. As a result, I have
no ability to use Alert actions using AeroGear, because there is no real way to customise
the behaviour the easy way.
The goal of this message is to start the discussion around this topic and maybe decide
what is better to do from Hawkular or AeroGear side. I’m adding Daniel and Summers to the
discussion as AeroGear Android developers, maybe they can elaborate a little and provide
ideas and / or details.
Artur.
[1]: http://www.hawkular.org/docs/rest/rest-alerts.html
<http://www.hawkular.org/docs/rest/rest-alerts.html>
2:23 a.m.
Hi Artur,
Hi everyone,
I’m trying to use Hawkular API with AeroGear for Android.
Just to remind everyone, the Hawkular Alerts API uses HTTP PUT requests for
actions such as resolve and acknowledge. Affected alert IDs are passed as a
HTTP query parameter. As such, if I want to resolve an alert with ID “oops”,
I need to do the following request:
http PUT :8080/hawkular/alerts/resolve?alertIds=oops
At the same time, AeroGear uses PUT requests more traditionally, appending
model ID to the request URL so it looks something like
“hawkular/alerts/resolve/oops”. As a result, I have no ability to use Alert
actions using AeroGear, because there is no real way to customise the
behaviour the easy way.
The goal of this message is to start the discussion around this topic and
maybe decide what is better to do from Hawkular or AeroGear side. I’m adding
Daniel and Summers to the discussion as AeroGear Android developers, maybe
they can elaborate a little and provide ideas and / or details.
What model can work better for your use case ?
If we pass the list of alertsId to resolve inside a json object can work better in that
scenario ?
Thanks,
Lucas
Artur.
[1]: http://www.hawkular.org/docs/rest/rest-alerts.html
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
2:41 a.m.
Hey Lucas,
Not really sure actually. What Daniel suggested and what is actually
supported at this point by AeroGear looks something like this.
http PUT /hawkular/alerts/resolve/ALERT-ID
Artur.
2:47 a.m.
Hey Lucas,
Not really sure actually. What Daniel suggested and what is actually
supported at this point by AeroGear looks something like this.
http PUT /hawkular/alerts/resolve/ALERT-ID
I'm thinking if we may maintain both approaches, one endpoint as you suggest for
individual alert resolution, and a second one with an object as payload with a list of
alert-id.
A common scenario might need to resolve a group of ids in one step.
Ok, I'm going to update this info in a formal JIRA.
Thanks for the feedback.
Lucas
2:54 a.m.
Yep, I understand. I will understand if you decide not to update API as
well :-) It would be great to provide the most universal API possible,
without adjusting to any specific tools.
I heard about batch requests [1] some time ago, maybe it can help.
[1]: https://developers.google.com/drive/web/batch
3 a.m.
I've created a JIRA to track this enhancement:
https://issues.jboss.org/browse/HWKALERTS-60
It's interesting to get feedback to see what is best approach.
I'm collecting all feedback to review whole REST API if needed.
Feel free to comment on the JIRA as well.
Thanks,
Lucas
----- Original Message -----
From: "Artur Dryomov" <artur.dryomov(a)gmail.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Cc: supittma(a)redhat.com
Sent: Tuesday, June 23, 2015 9:54:57 AM
Subject: Re: [Hawkular-dev] Alerts API
Yep, I understand. I will understand if you decide not to update API as well
:-) It would be great to provide the most universal API possible, without
adjusting to any specific tools.
I heard about batch requests [1] some time ago, maybe it can help.
[1]: https://developers.google.com/drive/web/batch
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
4129
days inactive
4132
days old
5 comments
2 participants
participants (2)
-
Artur Dryomov -
Lucas Ponce