3:58 a.m.
Hi everyone,
This year I am working on the Hawkular Android application as part of the
Google Summer of Code 2015 program.
This morning Heiko had merged two pull requests. The first one is important
and is related to the API update, hopefully you can use the latest Hawkular
version with the application at this point—well, at least the 1.0.0 Alpha 2
[1]. The second one is more minor, but helpful—you can now filter alerts by
time periods, just like the web UI [2].
I wanted to discuss future plans—mostly because the application itself is
working and all basic features are available. Most of all I would like to
receive some feedback regarding the direction of the future development.
And I totally understand that Hawkular itself is evolving and there are
more changes to come.
Major.
- Accounts. I need to investigate if it is possible at all, but multiple
accounts handling would be nice. If it is not, at least logging out should
be supported. There is some work done about that, but the discussion
suddenly calmed down [3].
- Navigation. I am not entirely sure that the current navigation handles
everything properly. For example, at the moment all alerts are shown when
browsing alerts. There should be some categorization based on resources,
but at moment there are no proper API calls supporting it. The only thing
we have is filtering via trigger IDs. Web UI solution is mostly a hack from
my perspective [4].
- Applications. This is a big one. I need to try to configure it and
play with the API to understand how it works and how can I adapt the
application to handle it.
Minor.
- Chart. Distinguish availability and threshold ones. Not sure if it is
possible in a flexible way, because Inventory at this point doesn’t show a
type in the Metric model.
- Chart. Make it more like the web one. I’m kind of limited by the used
chart library, plus it is tricky to handle large sets of data, especially
for months and years. Trying to dig through the TypeScript source code to
understand how the web UI works.
- Lists. Maybe add pull-to-refresh support. Purely cosmetic and utility
change, not sure if it will be useful actually.
Most likely I should restructure these points into GitHub issues and work
on them, but I wanted to receive some feedback if it is possible. What do
you want to see in the application? What do you think should be primary
goals at this point?
Thanks and have a nice week!
Artur.
[1]: https://github.com/hawkular/hawkular-android-client/pull/28
[2]: https://github.com/hawkular/hawkular-android-client/pull/29
[3]: https://github.com/hawkular/hawkular-android-client/pull/26
[4]:
https://github.com/hawkular/hawkular/blob/b61fc571bfff88a08621b088c79f3a2...
9:58 a.m.
Hi Artur,
At the alerting level the main ability to categorize, outside of playing
games with trigger names and things like that, is provided by Tags.
Tags can be applied to Triggers and are basically [category],name. You
can then query Triggers via tags, and also query alerts via the tags on
their owning triggers.
Because alerts have no inventory context, meaning it does not know about
resources, higher level API for tying together Resources/Triggers/Alerts
would need to be provided at the Hawkular level. And that is fine, I
think. So the questions become, "what would a helpful API look like"
and "where do we keep the relationships, in alert tags, resource
relationships,. etc"?
Open to ideas. Also, there is [HWKALERTS-62: Allow any data to store
contextual information] which could also come into play.
On 7/13/2015 4:58 AM, Artur Dryomov wrote:
* Navigation. I am not entirely sure that the current navigation
handles everything properly. For example, at the moment all alerts
are shown when browsing alerts. There should be some
categorization based on resources, but at moment there are no
proper API calls supporting it. The only thing we have is
filtering via trigger IDs. Web UI solution is mostly a hack from
my perspective [4].
1:16 p.m.
Hey Artur,
- Accounts. I need to investigate if it is possible at all, but
multiple
accounts handling would be nice. If it is not, at least logging out should
be supported. There is some work done about that, but the discussion
suddenly calmed down [3].
But that was mostly a "how do I do it in the UI" thing?
Logging out and logging in at different user and/or even switch
to a different server are not questioned as far as I am concerned.
- Applications. This is a big one. I need to try to configure it and
play with the API to understand how it works and how can I adapt the
application to handle it.
Well, what you see right now are not even really (what we mean with)
applications, but deployments with different aspects of them.
- Lists. Maybe add pull-to-refresh support. Purely cosmetic and
utility
change, not sure if it will be useful actually.
Or just a square reload button? But it seems that the pull to reload
pattern is pretty common these days.
What do
you want to see in the application? What do you think should be primary
goals at this point?
Certainly more inventory types.
And the navigation from resource -> metric names -> chart
could be different for me with the metric names being a dropdown
on top of the page. That would save one touch to see the
default metric for a resource.
Also (and I think you were talking about that earlier) it could be
pretty cool to have some swiping to be able to select the chart
display time (and some two finger spread to select the duration
shown to zoom in / out ).
Heiko
3520
days inactive
3520
days old
2 comments
3 participants
participants (3)
-
Artur Dryomov -
Heiko W.Rupp -
Jay Shaughnessy