Hi, We can capture App Type event as well. So the even stream would be updated as follows.
Tenant Id : Username(email) : Item : Action : Timestamp : Context (Application) : App Type : Comments thanks, dimuthu On Thu, Jul 31, 2014 at 4:07 PM, Dmitry Sotnikov <[email protected]> wrote: > Dimuthu, > > Are "comments" parameters of the action? For example, the type of > application user chose when creating the new app? > > That would be good to have so administrators know which app types are in > use in their App Factory deployment. > > Dmitry > > > On Thu, Jul 31, 2014 at 1:57 PM, Dimuthu Leelarathne <[email protected]> > wrote: > >> Hi, >> >> >> A sample set of events a user would do, >> >> User x logged in >> >> App home loads >> >> Clicked on “Add New Application” button >> >> Create application page loads >> >> Clicked upload/create from scratch >> >> Clicked “Create Application” >> >> App home loads >> >> Clicked on application tile >> >> Clicked on repo url >> >> Did a commit === Not by browser but by a Git client >> >> Set the production URL >> >> Edit description >> >> Click on expand icons on current status on home page >> >> Clicked on “Open URL” >> >> Clicked on “Open Issues” from home page >> >> Clicked “Delete Application” >> >> User home loads >> >> User x logged out >> >> >> *What we need to do* >> >> Record these user’s events with the objective of understanding user >> interactions with App Factory >> >> *What we need to understand about user interactions?* >> >> - How much time user spend to between start action and end action (Create >> application button and completing of that task) >> >> - What are the most frequent actions a user would perform >> >> - What are the actions user started but never completed and why? Session >> timeout, Hit Cancel, Or just browse away >> >> - What is the most frequently loaded page >> >> - What is the most frequently accessed application of a user? >> >> >> *This we are going record* >> >> Tenant Id : Username(email) : Item : Action : Timestamp : Context >> (Application) : Comments >> >> *Methodology* >> >> Each time an event happens we are going to keep it in the JavaScript data >> structure. Then these data will be transferred to backend >> >> - Periodically (5 minutes) with another action called “on the same page >> after 5 mins”- this is because if a session invalidates we can identify it >> by this action >> >> - Or each time the page unloads >> >> When backend receive(Jaggery) the data it will be published to the BAM. >> Then in the Java layer also we'll identify points that user would interact >> for example - commits and publish it to BAM. >> >> >> Any thoughts? >> >> thanks, >> dimuthu >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Dmitry Sotnikov > VP of Cloud; WSO2, Inc.; http://wso2.com/ > email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov > > Lean . Enterprise . Middleware > > <http://wso2.com/events/> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: [email protected] Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
