3:23 a.m.
Hello all,
I was doubtful if we gonna provide apk of android client of hawkular
through Google play store or user will have to compile for themselves. I
assume the case to be of play store.
And if that is the case then clients can not use their own google account
to setup push notifications for alerts as configration file is needed to be
inside apk.
I suggest that hawkular can provide one instance of firebase account for it
and all the hawkular servers will use the same.
With the workflow I suggest, there will not remain the need of setting up
unified push server to provide notification.
Steps :-
- With any user creation on any hawkular serve, there will be created a
32 Byte ID that we can assume to be unique.
- Any client that sign in to that user will retrieve that string and
will register to that as topic subscription.
- When ever a new alert is created. It will fire a HTTP request to
Firebase with unique id as toopic and Server key provided by hawkular
inbuilt.
- Rest work of manupulating the recieved alert will be handled on client
side.
Please write your views on this.
Thanks
Anuj Garg
1:35 p.m.
On Fri, Jul 29, 2016 at 4:23 AM, Anuj Garg <anuj1708(a)gmail.com> wrote:
Hello all,
I was doubtful if we gonna provide apk of android client of hawkular
through Google play store or user will have to compile for themselves. I
assume the case to be of play store.
+1
And if that is the case then clients can not use their own google account
to setup push notifications for alerts as configration file is needed
to be
inside apk.
+1
I suggest that hawkular can provide one instance of firebase account for it
and all the hawkular servers will use the same.
+1
With the workflow I suggest, there will not remain the need of
setting up
unified push server to provide notification.
+1 let's remove UPS from it and use Firebase directly.
Steps :-
- With any user creation on any hawkular serve, there will be created
a 32 Byte ID that we can assume to be unique.
Should we create a jira for Hawkular team implement it?
- Any client that sign in to that user will retrieve that string and
will register to that as topic subscription.
So, the idea is create a topic for the user ID? and him on this topic?
- When ever a new alert is created. It will fire a HTTP request to
Firebase with unique id as topic and Server key provided by hawkular
inbuilt.
Should we create a jira for Hawkular team implement it?
- Rest work of manupulating the recieved alert will be handled on
client side.
+1
Please write your views on this.
2 Things we need to think about
1) How 2 different users in the same server will receive the same alert,
like when hawkular website got down, you and me need to receive the same
alert.
2) We need to register all devices for the same user in the same topic.
Thanks
Anuj Garg
9:11 a.m.
From my current understanding of Hawkular, different user IDs do not
matter
as alerts generate on the base of tenants to which the trigger is
associated and tenants are shared between the users.
So we will need only one unique ID per server. There can be 2 ways for it :-
1. If we don't care for privacy then we can use the location (host+port)
as server ID as it will be unique for each server anyway. Plus no need to
pass that data to the client as it already knows this.
2. We can generate one ID per server instance. But then we will need the
client to know this value from somewhere.
So only thing client need is to subscribe to server ID and all the tenants
from which we wish to receive alerts from.
Aerogear action plugin will send FCM with "AND" topic condition of tenant
ID and server ID
2821
days inactive
2826
days old
3 comments
3 participants
participants (3)
-
Anuj Garg -
Daniel Passos -
Heiko W.Rupp